upgrade to v0.9.16

[zqhxuyuan]

xcm related:

• canonical reanchored location: closes: new reanchor compatible change #1762
  • relates to: Reanchor should return canonical location paritytech/polkadot#4470
  • I found it's difficult to setup config only to testcase, so I use integration-tests feature flag for now.
• statemine asset prefix location
  • relates to: Update XCM MultiLocation prefixes for assets paritytech/cumulus#831
  • also use integration-tests to testcase which make sure RMRK migration works.

removal Default:

• MaxEncodedLen & without_storage_info
  • stable-asset module should have this too, otherwise it'll compile error: update to v0.9.16 nutsfinance/stable-asset#14
• ParentIsPreset (not sure new cumulus release will include this yet)
• CheckNonZeroSender: CheckNonZeroSender #1662

client:

• cumulus consensus refactor

runtime new pallet:

• add pallet_preimage to pallet_scheduler
  • migration: Preimage registrar and Scheduler integration paritytech/substrate#10356
• add pallet_child_bounties to pallet_bounties(do not add for now as kusama runtime not added)

tests:

• kusama native asset: karura native asset test #1768
  • current karura and sibling both use same runtime, so their native asset both is KAR, need integration-tests to manual adapt/fixed the para_id to 2000
• test-service(version <= 0.9.15 has compile error of client type, so moved here)

---

upgrade guide:

• canonical reanchored location: before we upgrade, make sure bifrost already compatible. and current it's already done in bifrost side.
• statemine asset prefix location we don't need compatible because we use foreign_asset_id internal, but after statemine upgrade, we must change RMRK location on asset-registry from (1, X2(1000, GenealIndex(8))) to (1, X3(1000, PalletInstance(50), GeneralIndex(8)))

[sander2]

Sorry to intrude on your PR, but I have a question. Do you know if the following change is required as well? I suspect that maybe polkadot/substrate will automatically canonicalize it, in which case it doesn't matter, but tbh I am not completely sure where the new simplify function gets called. I'm asking because we use some very similar runtime code.

fn native_currency_location(id: CurrencyId) -> MultiLocation {
-    MultiLocation::new(1, X2(Parachain(ParachainInfo::get().into()), GeneralKey(id.encode())))
+    MultiLocation::new(0, X1(GeneralKey(id.encode())))
}

[zqhxuyuan]

don't need change native_currency_location(). as the new canonical reanchored only change the meaning of to-reserve/non-reserve case. i.e ParaB transfer token A to ParaA, from the point view of ParaA, the location is changed. But for the case of ParaA transfer token A to ParaB. we do not need to change native_currency_location() as xtokens will invoke reanchor, the for the point view of ParaB, the location not change, still got (1, 2000, A).

[sander2]

Another headsup: I found in kintsugi testing on rococo-local that we needed to canonicalize the chain-local assetids in the PerSecond Trader items

[zqhxuyuan]

Another headsup: I found in kintsugi testing on rococo-local that we needed to canonicalize the chain-local assetids in the PerSecond Trader items

👍 I'll revisit Trader config, as we're missing transfer native asset test, previous I add some code but delete them as I need to add integration-tests a few place. I think KarPerSecondOfCanonicalLocation should added to production case, not integration-tests case.