[manta] Bump upstream to v0.9.16

[ghzlatarev]

Description

closes: #374
closes: #388

• Upgrades to most recent Polkadot version v0.9.16
• Bump transaction_version because of changes to calls in pallet-parachain-system Look at the upgrade go-ahead and restriction signals paritytech/cumulus#517.
• System accounts can now only have a maximum number of consumers; once this limit is exhausted, any consumer-requiring operations will fail. This includes new asset-accounts. Insufficient asset quota and deposits paritytech/substrate#10382
• Changes to trie format and implementation. Switch to new trie format is done by changing the new state_version field of RuntimeVersion to 1. Dont't switch for now so start at 0. Inner hashing of value in state trie (runtime versioning). paritytech/substrate#9732
  • Logged issue: Switch to new trie format - Switch to new trie format #385
• Adds pallet_preimage and runs migration for Scheduler Preimage registrar and Scheduler integration paritytech/substrate#10356 The scheduler pallet can now be configured with pallet_preimage, and makes it possible to schedule a call (e.g. runtime upgrade) without immediately uploading it. Rather, you would give a hash of the call, and upload it later
  • Tested with try-runtime locally, because the production and testnet chains don't have the state_version field and try-runtime is expecting it.
  • Logged issue: Revisit deposit configurations in Manta/Calamari #386 - Set appropriate deposits for the Preimage deposit -
• Substrate pallets now need all storage items to implement MaxEncodedLen by default.Require MaxEncodedLen per default paritytech/substrate#10662 By using the macro#[pallet::without_storage_info], we skip generating storage info and can worry about this change later. It will be required for PoV benchmarks
  • Logged issue: Implement MaxEncodedLen wherever necessary Implement MaxEncodedLen wherever necessary #387
• Updated handling of xcm paths: Reanchor should return canonical location paritytech/polkadot#4470
• Client: cumulus consensus refactor
  - Introduce interface for relay chain interaction paritytech/cumulus#835
  - pov-recovery: Enable pov-recovery as well on full nodes paritytech/cumulus#927
  - Unify RelayChainInterface error handling and introduce async paritytech/cumulus#909
  - Statemint: Support running statemint only with ed25519 paritytech/cumulus#923
• New way of handling constants: pub const MaxLocks: u32 = 50; => ConstU32<50>. For now surely sticking to the old way, but logged an issue to migrate when feel like it Migrate to new method of declaring constants in Calamari/Manta #389
• Re-benchmark pallets

Cumulus diffs between - 05cc5f0e2acacc18796f45ffa3c7b4626fd1046d and 86f76c5619c64d1300315612695ad4b4fcd0f562

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (manta or dolphin) with right title (start with [Manta] or [Dolphin]),
• Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Wrote unit tests.
• Updated relevant documentation in the code.
• Re-reviewed Files changed in the Github PR explorer.
• If runtime changes, need to update the version numbers properly:
  • authoring_version: The version of the authorship interface. An authoring node will not attempt to author blocks unless this is equal to its native runtime.
  • spec_version: The version of the runtime specification. A full node will not attempt to use its native runtime in substitute for the on-chain Wasm runtime unless all of spec_name, spec_version, and authoring_version are the same between Wasm and native.
  • impl_version: The version of the implementation of the specification. Nodes are free to ignore this; it serves only as an indication that the code is different; as long as the other two versions are the same then while the actual code may be different, it is nonetheless required to do the same thing. Non-consensus-breaking optimizations are about the only changes that could be made which would result in only the impl_version changing.
  • transaction_version: The version of the extrinsics interface. This number must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. If this number is updated, then the spec_version must also be updated
• If needed, notify the committer this is a draft-release and a tag is needed after merging the PR.
• Verify benchmarks & weights have been updated for any modified runtime logics
• If needed, bump version for every crate.
• If import a new pallet, choose a proper module index for it, and allow it in BaseFilter. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.
• If needed, update our Javascript/Typescript APIs. These APIs are offcially used by exchanges or community developers.
• If we're going to issue a new release, freeze the code one week early(it depends, but usually it's one week), ensure we have enough time for related testing.

[Dengjianping]

LGTM!