[xcm] GlobalConsensusConvertsFor for remote relay chain (based on pevious GlobalConsensusParachainConvertsFor)

[bkontur]

Relates to: paritytech/parity-bridges-common#2401

Will be used to generate accountId as sovereign account of remote relaychain, e.g. for setting pallet_assets::ForeignAssets owner/issuer/freezer/admin for wrappedDOT/wrappedKSM

e.g.: on AssetHubKusama for foreign asset with MultiLocation { parents: 2, X1(GlobalConsensus(Polkadot)) } owner accountId will be

GlobalConsensusConvertsFor::<UniversalLocation, [u8; 32]>::conver_location(
    MultiLocation { parents: 2, X1(GlobalConsensus(Polkadot)) }
)

and also this GlobalConsensusConvertsFor could be added to the LocationToAccountId on AssetHubs, which will allow to process xcm::Transact(pallet_assets::set_team/...) over bridge from remote relay chain as owner of its wrapped representation of native asset

[bkontur]

bot rebase

[paritytech-processbot]

Rebased

[joepetrowski]

Edited for clarity, however I don't particularly agree with this comment. It does not create commonalities between chains; actually it says that one chain will have the same 32-byte AccountId in other consensus systems (that use 32-byte account IDs). If this chain has a security incident, that would have effects in many other chains, but it does not put anything in common between the local chain and the "global" chain.

Unless I am missing something, I would delete this comment.

Suggested change

	/// WARNING: This results in the same `AccountId` value being generated regardless
	/// of the relative security of the local chain and the Relay-chain of the input
	/// location. This may not have any immediate security risks, however since it creates
	/// commonalities between chains with different security characteristics, it could
	/// possibly form part of a more sophisticated attack scenario.
	/// WARNING: This results in the same `AccountId` value being generated regardless of the relative
	/// security of the local chain and the security of the input location. This may not have any
	/// immediate security risks; however, because it creates commonalities between chains with
	/// different security characteristics, it could possibly form part of a more sophisticated attack
	/// scenario.

[svyatonik]

LGTM

[bkontur]

bot rebase

[paritytech-processbot]

Rebased

[bkontur]

bot rebase

[paritytech-processbot]

Rebased

[paritytech-cicd-pr]

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/3309519

[bkontur]

bot merge