Upgrade to polkadot v1.1.0

[rimbi]

What does it do?

Upgrades the dependencies

• polkadot-sdk
• frontier
• moonkit
• orml
• pallet-crowdloans

to the version moonbeam-polkadot-v1.1.0.

What important points reviewers should know?

Breaking Changes

• Eth::new accepts two additional parameters:
  • pending_create_inherent_data_providers: which requires time inherent and ,in our case, ParachainInherentData provider. Since these are needed in a pending context, providing dummy values is enough.
  • pending_consensus_data_provider: Through which we provided nimbus author id (by getting it from the last best block) and vrf digests.
• The number of instructions in an XCM message is limited to 100. This effects the test in test/suites/dev/test-xcm-v3/test-mock-dmp-queue.ts.
• try-runtime subcommand has been removed and migrated to the standalone-cli.
• AllowPaidExecutionFrom barrier now prevents multiple currency transfers.
• The following crates in the polkadot-sdk has new names:
  • xcm -> staging-xcm
  • xcm-executor -> staging-xcm-executor
  • xcm-builder -> staging-xcm-builder
  • kusama-runtime -> staging-kusama-runtime
• In accordance with the above changes the XcmVersionedXcm message in the ts tests has been renamed to StagingXcmVersionedXcm
• In frame_system::Config,
  • the Index was renamed to Nonce
  • BlockNumber, Header and HoldIdentifier were removed
  • Block, Aliasers and RuntimeHoldReason were added
• paras::Config has a new associated type OnNewHead
• hrmp::Config has a new associated type ChannelManager
• pallet_message_queue::Config has a new associated type QueuePausedQuery
• build_storage and assimilate_storage is now provided via sp_runtime::BuildStorage instead of frame_support::traits::GenesisBuild
• The use of xcm_executor::traits::Convert was replaced with xcm_executor::traits::ConvertLocation whose APIs differ.
• Removal of native runtime execution required to enable improved_panic_error_reporting feature in sp_io and chain-error in parity-scale-codec to pass certain test cases.
• hrmp::WeightInfo::force_open_hrmp_channel accepts a new u32 argument
• WeightTrader::buy_weight method takes an additional XcmContext parameter.
• pallet_xcm_benchmarks::generic::Config requires a new method alias_origin

Is there something left for follow-up PRs?

• Replace depricated start_full_node and start_collator APIs
  
• Investigate the issue with the chopsticks
• The feature flags such as moonriver-native should be renamed.

What alternative implementations were considered?

Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?

• Polkadot-sdk
• Moonkit
• orml
• frontier

What value does it bring to the blockchain users?

[notlesh]

Looks good so far (I know it's not done yet :) )

[github-actions]

Coverage generated "Tue Oct 10 10:10:49 UTC 2023":
https://d3ifz9vhxc2wtb.cloudfront.net/pulls/2499/html/index.html

Master coverage: 87.39%
Pull coverage:

[notlesh]

Looks good so far, haven't made it through everything yet but wanted to push my comments so far.

[notlesh]

LGTM. I left some comments that are worth reviewing though :)