Onchain task for BNB AMB

[liu-zhipeng]

Problem

Replace BNB multichain connector

Context

• BNB AMB (BSC) #4517
  https://connext.notion.site/Pre-Spec-for-BSC-Amb-3578aea3d7a4485eb63498ece0b22fbd

Action Items

• HubConnector for Wormhole
• SpokeConnector for Wormhole
• Forge Tests: Unit test covering all fuzz cases
• E2E testing
• HH tasks for deployment and test
• Init script
• deployment at Testnet for initial testing for the Wormhole contracts
• Deploy Connector for Mainnet
• Deploy Connector for spoke

Acceptance criteria

• E2E working at BNB, ARBITRUM, and ETHEREUM (Fork Mainnet).
• Succesful xcall() via HH tasks
• Succesful sendMessage() via HH tasks
• Succesful propagate() via HH tasks
• Succesful proveAndProcess() via HH tasks
• Does not double-reconcile transfers ( MessageStatus checks are overridden on new spoke deploy)
• Does not double-process transfers (should not cause many transfers to be proveAndProcessed again. this will require offchain verification against newly deployed subgraphs)

Fixes #4623

[rhlsthrm]

Verified that old message cannot be processed by new connector, so double spend is not an issue.

[rhlsthrm]

Created forge test, requested review, R4R.

[rhlsthrm]

Contract is done, need to test on testnet, but Wormhole does not support Goerli. Need to either test on other testnets or mainnet.

[rhlsthrm]

Verified messaging from BNB to ETH, still verifying ETH to BNB.

[LayneHaber]

txs + costs:

ETH -> BSC 
 - 0.000254019196160768 ETH ($0.48) paid on ETH 
 - 0.000713894285678591 BNB ($0.17) refund
 - total: $0.31 paid

BSC -> ETH
 - 0.096724973432518598 BNB ($23.07) paid on BSC
 - 0.00510868 ETH           ($9.7) refund
 - total: $13.37
 - txs:
https://etherscan.io/tx/0x580a3dcec415417b949e947e1335b58b6eeb31f128136b48a3b0c35e0570cbfa
https://bscscan.com/tx/0xc5478c6cacb5fffc2ced78201dd1d6e5d7f6e2b3ab41f89c5b30cc4788e51790

[rhlsthrm]

Ready for audit, will not deploy and init as part of this task.

[alexwhte]

we are moving deployment and testing into separate issue

Deploy Connector for Mainnet
Deploy Connector for spoke
Acceptance criteria
Does not double-reconcile transfers ( MessageStatus checks are overridden on new spoke deploy)
Does not double-process transfers (should not cause many transfers to be proveAndProcessed again. this will require offchain verification against newly deployed subgraphs)