feat: vault bridge v1.1.0

[ZeroEkkusu]

Vault Bridge v1.1.0

1. Create customized, upgradeable LayerZero OFT Adapter contracts
2. Add support for new Bridge Provider (LayerZero)
3. Add support for Bridged USDC Standard (LayerZero)
4. Miscellaneous improvements and fixes
5. Improve Bridge Provider documentation to aid Sales Team
6. Improve deployments tracking to include all mainnets, testnets, and devnets
7. Deploy permissionless faucet for mock underlying tokens

[0xCVH]

@web3security when you review this PR, can you please check and comment on the diff between the Certora auditted version and this (if any). Thanks

[ZeroEkkusu]

@0xCVH @web3security This PR needed to be rebased, as you can see from the commit history. I highly recommend you clone the repository twice, and checkout the first one to the branch/commit that Certora indicated as the final in the report, checkout the second one to this branch/commit, and the run the following command in terminal:

diff -qr --exclude=".git" vault-bridge-certora vault-bridge-pr

[web3security]

LGTM.

Here some relevant information about the review:

• Due to rebase with 229 commits, I had reviewed the diff between certora audit version (commit 950e64d) and last commit of this PR (d863a96) that was pushed today.
• The diff can be found here: https://github.com/agglayer/vault-bridge/compare/950e64d..d863a96
• I also made a manual diff myself locally as suggested by Zero. (attached)

Here some recommendations anyway:

• Deployment scripts should include addresses that are basic for this to run or simulate. I had to ask them through DM but in general I do recommend pushing addresses (or using input.json files as this repo was using at the beginning) so we avoid human error while using it. At least we need to ensure there is no error in the process since the security review.
• Related to the above, it is recommended to enforce Layerzero endpoints usage from its website: Ethereum (https://docs.layerzero.network/v2/deployments/chains/ethereum) and Katana (https://docs.layerzero.network/v2/deployments/chains/katana)
• Those not very familiar with the codebase will likely misunderstand that DeployNonDefaultOftAdapters.s.sol script is to deploy Ethereum mainnet instances (named primary chain) and DeployNonDefaultMintBurnOftAdapters.s.sol is for Katana's or secondary chains' instances.
• It is worth mentioning that because Katana will use 0.5.1 the setBridge is not required so it is ok that last commit removed such reference. Anyways, future deployments would use it for other secondary chains, so this script should be reviewed in that sense.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.