feat: deploy EURm to Monad

[nvtaveras]

Summary

• Deploy EURm stable token to Monad
• Deploy NTTHelper for EURm on Monad and Celo
• Some fixes on the token deployment scripts

Addresses

• EURm Spoke on Monad: 0x4D502d735B4C574B487Ed641ae87cEaE884731C7
• NTTManager: 0x5F8a1e50F83f53951B89Fc73Ead80b27045C67fd
• WormholeTransceiver: 0x6467cfCA82184657F32F1195F9a26b5578399479

[cursor]

This PR deploys the Monad EURm spoke token and adds EURm NTT helper metadata for Monad/Celo, with a small cleanup to the spoke deployment/import scripts.

.treb/registry.json

• 🟡 Important: line 618 adds the new Monad EURm proxy address, but the repo’s generated contracts package was not regenerated alongside it. packages/contracts/contracts.json and packages/contracts/src/EURm.ts still only expose EURm on chain IDs 42220 and 11142220, so downstream consumers using @mento-protocol/contracts will not see the new chain 143 deployment after this merges.

Final verdict: 🚫 Needs changes

  

_{Sent by Cursor Automation: PR Review}

[cursor]

The deployment registry is being updated here, but the generated contracts package was not regenerated in the same PR. Right now packages/contracts/contracts.json and packages/contracts/src/EURm.ts still only include EURm for 42220 and 11142220, so downstream code using @mento-protocol/contracts will miss the new Monad address after merge.

Please run the contracts package generator and commit the resulting packages/contracts/* updates together with this registry change.