Support bridged token transfers from any chain

[IkerAlus]

At the moment the API does not allow the user to set a global consensus systems as destination of the transfers (in order to perform a transfer of assets to a different ecosystem via the Bridge Hub).

To support this feature, the input params of the API will need to be adapted to a string beyond just the paraID as it is currently. Potentially, the destination address format/typing may need to be expanded too.

In terms of directions, it may make sense to introduce two (or three) new directions:

• systemToBridge (should be covered by the new transferAssets call of pallet XCM.
• paraToBridge (currently not supported by paras runtime).
• RelayToBridge (to transfer the native DOT/KSM to a different eco).

Related issue: #371

[IkerAlus]

As commented recently the paraToBridge direction should be already supported in certain parachains on mainnet (f.e., moonbeam, mythos, astar and byfrost) since the call transfer_assets_using_type_and_then has been already enabled in their runtimes, and assuming execution fees on Asset Hub step are paid in an asset qith a liquidity pool with DOT (f.e. USDC/T)

[andrew-ifrita]

Marking as won't fix as we are dropping support for asset-transfer-api in favor of ParaSpell. See more in this issue: #652