Add AssetTransferFilter trait for configuring transfer types.
Implement it for XcmExecutor based on existing executor teleports and
reserves configuration.
Filter assets on pallet-xcm::limited_teleport_assets() based on above.

…erves

'reserve_transfer_assets()' assumed all provided `assets` (fees included)
have same, local reserve.

This commit enhances the extrinsic to support various scenarios:
- transferring assets with reserve on destination,
- transferring assets with reserve on remote/third-party chain,
- transferring assets with reserve different than the reserve of the
  asset to be used as fees - meaning can use to transfer random asset with
  random reserve while using DOT for fees on all involved chains, even
  if local chain is NOT a reserve location of DOT (aka most chains),
- transferring assets with any type of local/dest/remote reserve while
  using fees which can be teleported between involved chains.

All of the above is done by pallet inner logic without the user having to
specify which scenario/reserves/teleports/etc. The correct scenario and
corresponding XCM programs are identified, and respectively, built automatically
based on runtime configuration of trusted teleporters and trusted reserves.

Current limitations:
- while `fees` and "non-fee" `assets` CAN have different reserves (or fees CAN
  be teleported), the remaining "non-fee" `assets` CANNOT have different
  reserve locations (this is also implicitly enforced by
  `MAX_ASSETS_FOR_TRANSFER=2`, but this can be safely increased in the future).
- `fees` and "non-fee" `assets` CANNOT have **different remote** reserves (this
  can also be supported in the future, but adds even more complexity while
  possibly not being worth it - we'll see what the future holds).

…eported fee

…re intended

…et-xcm-fully-support-reserve-transfers

… instead of pallet_xcm

…et-xcm-fully-support-reserve-transfers

…et-xcm-fully-support-reserve-transfers

…et-xcm-fully-support-reserve-transfers

…et-xcm-fully-support-reserve-transfers

…appended ClearOrigin

…et-xcm-fully-support-reserve-transfers

…ot-sdk-update-v2-reserve-asset-transfer

# Conflicts:
#	cumulus/parachains/runtimes/assets/asset-hub-rococo/src/xcm_config.rs
#	cumulus/parachains/runtimes/bridge-hubs/bridge-hub-rococo/src/xcm_config.rs

…et-xcm-fully-support-reserve-transfers

This reverts commit c82330b.

…allet-balances instead

…erve-asset-transfer-fixed

# Conflicts:
#	cumulus/parachains/runtimes/assets/common/src/matching.rs
#	cumulus/parachains/runtimes/bridge-hubs/bridge-hub-rococo/src/xcm_config.rs

Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>

Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>

* adds message queue pallet

* adds outbound queue

* fix compiler errors

* adds snowbridge to rococo bridgehub

* asset hub rococo

* asset hub rococo

* finishing up applying changes

* fix incorrect pallet-xcm imports

* fixing tests

* adds upstream changes

* cleanup comments, fix upgrade gateway test

* attempts to fix xcm config

* fixes send token

* fmt

* fixes after rebase

* fixes after rebase

* correct relay network check

---------

Co-authored-by: claravanstaden <Cats 4 life!>

Co-authored-by: Branislav Kontur <bkontur@gmail.com>

Co-authored-by: Branislav Kontur <bkontur@gmail.com>

Co-authored-by: Branislav Kontur <bkontur@gmail.com>

Co-authored-by: Branislav Kontur <bkontur@gmail.com>