Stable2503

[vedhavyas]

Migrate from stable2412 to stable 2503 latest. Our fork is updated accordingly with necessary patches applied on top.
Some of the patches can be pushed upstream and will send a patch once I'm finished with migration.

PR aims to avoid behavior change as much as possible. New features are not included if not straightforward and maybe added in follow-up PRs

Changes

• Major is coming from scale-codec with DecodeWithMemTracking marker trait that needs to be added to our types that cross the runtime boundary to client.
• Frontier added a new host function ProofSize which it uses to get the measure proof size of the ext rather than an estimation unlike before. More here polkadot-evm/frontier@d5755b5
• Network start is no more required
• New utility calls and multisig calls and benchmarking them was required.
• New if_else utility call is added where ext contain default Call and Fallback back if default fails. This would be tricky to handle for object mapping and left a TODO for later PRs
• You will now see a warning when compiling Runtime to migrate to wasm32v1-none. I did not want to take migration to new target yet until we are the sure the rest of the upgrade is compatible.

TODOs

• Ensure tests are not failing
• Tests both Consensus and Domain locally
• Ensure no migrations
• Devnet
  • Deploy with previous release and old runtime
  • Check Client compatibility
  • Check Runtime compatibility through runtime upgrade
    • Consensus Runtime Is Compatible with old clients without Domains
    • EVM domain runtime is NOT compatible with old clients due to the host function and all the nodes will have to migrate to new Node. Consensus clients also needs to migrate due to fraud proof verification and fails on missing host functions
• Test Client on Chronos
• Test Client on Mainnnet

I'm leaving this PR as draft until Devnet TODO is complete but please do review in the meantime

Migration plan is listed here - https://www.notion.so/subspacelabs/Stable-2503-2cc0bae47e9580cd9642ca225d91797c

Code contributor checklist:

• I have read, understood and followed contributing guide

[immunefi-magnus]

🛡️ Immunefi PR Reviews

We noticed that your project isn't set up for automatic code reviews. If you'd like this PR reviewed by the Immunefi team, you can request it manually using the link below:

🔗 Send this PR in for review

Once submitted, we'll take care of assigning a reviewer and follow up here.

[0xjeremyfrank]

LGTM. Can we add the detailed mainnet deployment strategy to the PR description?

[vedhavyas]

@jfrank-summit need another review. Recent farmerless dev changes are now included and fixed the RPC provider that was failing in the merge-queue