Feat: Polkadot stable2407 to stable2409 upgrade

[Aideepakchaudhary]

Description

This PR is upgrading Runtime's and Node's dependencies from Polkadot-SDK release stable2407 to stable2409

Notes

Relevant upgrade's notes and comments.

• Breaking changes

  • [https://github.com/Reactive syncing metrics paritytech/polkadot-sdk#5410]: Reactive syncing metrics
  • [https://github.com/Tx Payment: drop ED requirements for tx payments with exchangeable asset  paritytech/polkadot-sdk#4488]: Tx Payment: drop ED requirements for tx payments with exchangeable asset
  • [https://github.com/MaybeConsideration extension trait for Consideration paritytech/polkadot-sdk#5384]: MaybeConsideration extension trait for Consideration

• Potential Breaking changes

  • [https://github.com/[Assets] Call implementation for transfer_all paritytech/polkadot-sdk#4527]: Call implementation for transfer_all
  • [https://github.com/Balances Pallet: Emit events when TI is updated in currency impl paritytech/polkadot-sdk#4936]: Balances Pallet: Emit events when TI is updated in currency impl
  • [https://github.com/Tx Payment: drop ED requirements for tx payments with exchangeable asset  paritytech/polkadot-sdk#4488]: Tx Payment: drop ED requirements for tx payments with exchangeable asset

• Kindly refer to the official Polkadot release report for further details: Polkadot stable2409

• Polkadot release analysis : Polkadot stable2409 analysis

Process

• Bump workspace dependencies
• Fix issues
• Bump spec_ver for both testnet and mainnet Runtime.
• Bump node version if there were changes in the node. TBD

Codebase Upgrade Acceptance Criteria

• cargo check passes
• cargo test passes
• cargo build on -- release profile correctly builds
• try-runtime and runtime-benchmarks features compile
• Single node spinned up from binary works and generates blocks
• Zombienet network with 2 peers spawned with block-production config file generates blocks.

Runtime & Node Upgrade Acceptance Criteria

• Runtime upgrade works on Zombienet

• Node upgrade works on Zombienet

• Runtime upgrade works on Chopsticks

  • Testnet
  • Mainnet

• Try-runtime passes with no pending migrations

  • Testnet
  • Mainnet

---

<!--- PR TEMPLATE CONTENT STARTS HERE -->

Types of Changes

Please select the branch type you are merging and fill in the relevant template.

<!--- Check the following box with an x if the following applies: -->

• Hotfix
• Release
• Fix or Feature

Fix or Feature

<!--- Check the following box with an x if the following applies: -->

Types of Changes

<!--- What types of changes does your code introduce? -->

• Tech Debt (Code improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Dependency upgrade (A change in substrate or any 3rd party crate version)

Migrations and Hooks

<!--- Check the following box with an x if the following applies: -->

• This change requires a runtime migration.
• Modifies on_initialize
• Modifies on_finalize

Checklist for Fix or Feature

<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

• Change has been tested locally.
• Change adds / updates tests if applicable.
• Changelog doc updated.
• spec_version has been incremented.
• network-relayer's events have been updated according to the blockchain events if applicable.
• All CI checks have been passed successfully

Checklist for Hotfix

<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

• Change has been deployed to Testnet.
• Change has been tested in Testnet.
• Changelog has been updated.
• Crate version has been updated.
• spec_version has been incremented.
• Transaction version has been updated if required.
• Pull Request to dev has been created.
• Pull Request to staging has been created.
• network-relayer's events have been updated according to the blockchain events if applicable.
• All CI checks have been passed successfully

Checklist for Release

<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

• Change has been deployed to Devnet.
• Change has been tested in Devnet.
• Change has been deployed to Qanet.
• Change has been tested in Qanet.
• Change has been deployed to Testnet.
• Change has been tested in Testnet.
• Changelog has been updated.
• Crate version has been updated.
• Spec version has been updated.
• Transaction version has been updated if required.
• All CI checks have been passed successfully

[ayushmishra2005]

Please address this

#442 (review)

[ayushmishra2005]

#444 (comment)

[ayushmishra2005]

@Aideepakchaudhary Please address existing comments.