Feat: Polkadot v1.5 to v1.6 upgrade

[Aideepakchaudhary]

Description

This PR is upgrading Runtime's and Node's dependencies from Polkadot-SDK release v1.5.0 to v1.6.0

Notes

Relevant upgrade's notes and comments.

• Added RuntimeTask type in frame_system config.
• Performed the migration of a FRAME pallet: pallet_identity .
• Please validate the following values that are hardcoded in the code:
  • MaxControllersInDeprecationBatch: In pallet staking's config for both the runtimes (cere and cere-dev)
  • PendingUsernameExpiration, MaxSuffixLength, MaxUsernameLength, UsernameAuthorityOrigin : In pallet Identity config for both the runtimes (cere and cere-dev)
  • IDENTITY_MIGRATION_KEY_LIMIT: we passed this value in the migration of pallet_identity.
• Breaking changes:
  • Rename ExportGenesisStateCommand to ExportGenesisHeadCommand and make it respect custom genesis block builders
  • Staking: Add deprecate_controller_batch AdminOrigin call
  • pallet-vesting: Configurable block number provider
  • Tasks: general system for recognizing and executing service work
  • pallet-sudo: Accept Root origin as valid sudo
  • [NPoS] Remove better solution threshold for unsigned submissions
  • Add Authorize Upgrade Pattern to Frame System
  • proposer: return optional block
• Kindly refer to the official Polkadot release report for further details: Polkadot v1.6.0
• Polkadot release analysis : Polkadot v1.6.0 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