Upgrade to polkadot-sdk v1.11.0

[Kailai-Wang]

Context

As topic.

Some notes:

• xcm needs an overhaul, we are way behind (it's v4 now), plus we don't use it actively, so I turn most of the settings "off", as well as integration tests - @wangminqi please double-check the config to make sure there's no token transfer via XCM possible
• rococo runtime is removed
• orml is dismissed, it seems the forked branch would still introduce compile errors. The original orml uses crates.io based deps. The OrderedSet is copied over manually @wangminqi
• sp_core_hashing introduces std feature unintentionally, thus superseded by sp_core::hashing
• the node code is based on cumulus template code, some more RPC methods are introduced
• rust toolchain is upgraded to 1.81
• the finalisation delay is fixed
• feature propagation is fixed using zepter

Due to re-org, sometimes (especially in the dev) you can see tx status Retracted, but eventually it will be finalised. To deal with that in the enclave registration, I've forked https://github.com/Kailai-Wang/substrate-api-client/tree/polkadot-v0.9.42-litentry to allow Retracted status - base repo has something similar too: scs/substrate-api-client#807

As a (partial) consequence, I need to wait for Finalized status (instead of InBlock) in the account funding in the worker initialisation.

See also: https://substrate.stackexchange.com/questions/8872/when-is-a-transaction-retracted/8873#8873

Main files to review:

• files under parachain/node/
• litentry/paseo runtime configurations
• worker changes

[linear]

P-1165 One extra block delay in finalising parachain tx

[wangminqi]

XCM part LGTM

[BillyWooo]

LGTM. Thanks.

[Kailai-Wang]

There seems to be some race conditions regarding parachain ext submission - it can be related to the missing parachain events that we found earlier.

I'm trying to add more logs to debug it, so don't merge it now