Introduce Tinkernet multisig XCM configs to xcm-builder

[arrudagates]

This PR is a second attempt at introducing the Tinkernet XCM configs into xcm-builder and the Kusama/Rococo runtimes. For more information, refer to the original PR #7165.

This new PR comes with small changes to the location of the configs within xcm-builder in an attempt to make their relation to Kusama and Kusama parachains more explicit.

I also welcome discussions on different ways to implement this, particularly the point made by @gavofyork that these should make use of UniversalOrigin (#7165 (comment)), however it is not very clear from existing XCM documentation how this is supposed to work, and it appears it's not supported in Kusama/Rococo yet (#7165 (comment))

[arrudagates]

@ggwpez @sam0x17 @KiChjang @kianenigma @rphmeier
Since you reviewed the previous PR, I would like for you join discussions and, if possible, continue to provide reviews for this one.

[arrudagates]

Implementation of the configs in the Kusama/Rococo runtimes has been removed in preparation of the runtimes moving to polkadot-fellows/runtimes, but this still needs to be added to xcm-builder, as we have teams waiting to pull the configs from xcm-builder.

[KiChjang]

As mentioned in Element, the previous point made by Gav still stands -- the code being introduced here is too opinionated to be in the xcm-builder directory. Closing.