feat(protocol): implement Bridge.isMessageFailed

[dantaik]

On the source chain of a message, function isMessageFailed can verify if a message has been failed on the destination chain.

A test shall be added later in a separate PR.

[codecov]

Codecov Report

Merging #13004 (efc48ec) into main (07debb7) will decrease coverage by 0.53%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main   #13004      +/-   ##
==========================================
- Coverage   66.41%   65.89%   -0.53%     
==========================================
  Files         112      112              
  Lines        3052     3064      +12     
  Branches      363      368       +5     
==========================================
- Hits         2027     2019       -8     
- Misses        948      969      +21     
+ Partials       77       76       -1     

Flag	Coverage Δ		*Carryforward flag
bridge-ui	92.61% <ø> (ø)		Carriedforward from 07debb7
protocol	58.34% <0.00%> (-0.95%)	⬇️
relayer	69.10% <ø> (ø)		Carriedforward from 07debb7
ui	100.00% <ø> (ø)		Carriedforward from 07debb7

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files	Coverage Δ
packages/protocol/contracts/bridge/Bridge.sol	51.85% <0.00%> (-4.15%)	⬇️
...s/protocol/contracts/bridge/libs/LibBridgeData.sol	100.00% <ø> (ø)
...protocol/contracts/bridge/libs/LibBridgeStatus.sol	60.00% <0.00%> (-40.00%)	⬇️
...ges/protocol/contracts/libs/LibAnchorSignature.sol	89.47% <0.00%> (-10.53%)	⬇️
...es/protocol/contracts/thirdparty/LibMerkleTrie.sol	83.13% <0.00%> (-7.23%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dantaik]

@davidtaikocha somehow integration & genesis tests are failing. Can you take a look?

[davidtaikocha]

@davidtaikocha somehow integration & genesis tests are failing. Can you take a look?

Opened a PR to fix this: #13006 , looks like go-ethereum pushed a new latest tag image 10 hours ago, but they didn't release a new version of go-ehtereum (+ corresponding change logs )... and that newly pushed latest tag image can not be started successfully, so i changed the image tag to the current latest version tag v1.10.26 in that PR for now.