[EVM] Add 1.0 bridging interface to COA

[sisyphusSmiling]

Closes: #5663

This PR introduces bridge functionality to the COA resource, enabling a caller to bridge owned NFTs & FTs between VMs. These requests are routed from the calling COA to a BridgeRouter implementation which is stored in the EVM contract account. This resource encapsulates and safeguards a Capability on a BridgeAccessor implementation - defined in a bridge contract and stored in the bridge account - to which the BridgeRouter routes bridge requests.

The BridgeAccessor (not in scope for this PR but can be seen in onflow/flow-evm-bridge#28) then passes routed calls through to the VM bridge. Via these new interfaces and their stored implementations, the EVM contract can be integrated with the bridge.

Note that simply updating the EVM contract with these changes isn't sufficient to integrate with the bridge as calls to borrowBridgeAccessor will revert if a BridgeRouter is not saved with a valid BridgeAccessor Capability. To fully integrate, the bridge contracts will need to be deployed, a BridgeAccessor Capability published for the EVM contract account, and the published Capability will need to be saved in a BridgeRouter stored at the hardcoded storage path of /storage/evmBridgeRouter. Between the EVM update and the storage of the BridgeRouter, any bridge-related COA calls will simply fail.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.53%. Comparing base (39f59b1) to head (76b072d).
Report is 551 commits behind head on feature/stable-cadence.

Additional details and impacted files

@@                    Coverage Diff                     @@
##           feature/stable-cadence    #5664      +/-   ##
==========================================================
+ Coverage                   55.78%   58.53%   +2.74%     
==========================================================
  Files                         997       96     -901     
  Lines                       98760     8129   -90631     
==========================================================
- Hits                        55094     4758   -50336     
+ Misses                      39400     2869   -36531     
+ Partials                     4266      502    -3764     

Flag	Coverage Δ
unittests	58.53% <ø> (+2.74%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[turbolent]

Nice! Should this also be on master?

[sisyphusSmiling]

@turbolent I suppose it should, though I'm not sure how we're deciding what features live on master vs feature/stable-cadence

[turbolent]

@sisyphusSmiling AFAIK, so far all EVM features are on master. feature/stable-cadence only differs in terms of Cadence 1.0 support (for example, the EVM contract has entitlements, which are not supported pre-Cadence 1.0).

Maybe rebase on master (without entitlements), and then once we merge/sync master into feature/stable-cadence (fairly frequently), we can make Cadence 1.0-adjustments, like adding entitlements.

[sisyphusSmiling]

@turbolent had some issues trying to rebase on master with this branch. Thinking I'll close this PR and open a new one with a branch upstream from master.

[turbolent]

@sisyphusSmiling Sounds good, either way works! Also happy to help with rebasing this PR if you want

[sisyphusSmiling]

Closing in favor of #5716