Bump upstream to v0.9.17

[Dengjianping]

Description

closes: #422

Polkadot:

• Optimized weights: Optimized weights paritytech/substrate#10692
• Add a new host function for reporting fatal errors: Add a new host function for reporting fatal errors; make WASM backtraces readable when printing out errors paritytech/substrate#10741
• Revert connectivity fix 0.9.17: Revert connectivity fix 0.9.17 paritytech/polkadot#4943
• Allow two parachains to swap: Allow two Parachains to swap paritytech/polkadot#4772
• Add proxy type Society for Kusama: Add proxy type for Kappa Sigma Mu paritytech/polkadot#4851

Substrate:

• Optimized weights: Optimized weights paritytech/substrate#10692
• Add a new host function for reporting fatal errors: Add a new host function for reporting fatal errors; make WASM backtraces readable when printing out errors paritytech/substrate#10741
• Add maxencodelen to implement_per_thing!: Add MaxEncodeLen to implement_per_thing! paritytech/substrate#10715
• wasm-builder: Fall back to release profile for unknown profiles paritytech/substrate#10775
• Upgradable contracts using set_code function: Upgradable contracts using set_code function paritytech/substrate#10690

Cumulus:

• Repalce cli crate structopt with clap: Bump clap from 3.0.7 to 3.1.1 paritytech/cumulus#1035
• Introduce rpc client for relay chain full node: Introduce rpc client for relay chain full node paritytech/cumulus#963.
• Fix parachain block time degradation: Revert connectivity fix 0.9.17 paritytech/polkadot#4943
• Add the ability to suspend or resume XCM execution on the XCMP queue: Add the ability to suspend or resume XCM execution on the XCMP queue paritytech/cumulus#896

Ours:

• Type, ParentIsDefault -> ParentIsPreset
• Cli tool, Replace structopt with clap

---

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.
• Added one line describing your change in <branch>/CHANGELOG.md
• 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.
• Check if inheriting any upstream runtime storage migrations. If any, perform tests with try-runtime.

[Dengjianping]

Wait for this pr #435

[Dengjianping]

cannot sign off previous commits