feat(xcm): add xcm topic id wrappers to router and barrier

[XY-Wang]

This PR adds the WithUniqueTopic and TrailingSetTopicAsId wrappers, introduced in paritytech/polkadot#7234, to the XCM Router and Barrier respectively.

This will allow for easier tracking of XCM, especially in the case of multi-hop messages where the message hash differs on each leg.

More detailed explanation: https://substrate.stackexchange.com/questions/1893/is-there-an-id-for-xcm-message/1906#1906

The implementation mirrors that of the system parachains:

https://github.com/polkadot-fellows/runtimes/blob/7b096c14c2b16cc81ca4e2188eea9103f120b7a4/system-parachains/asset-hubs/asset-hub-polkadot/src/xcm_config.rs#L295

https://github.com/polkadot-fellows/runtimes/blob/7b096c14c2b16cc81ca4e2188eea9103f120b7a4/system-parachains/asset-hubs/asset-hub-polkadot/src/xcm_config.rs#L477

[jak-pan]

We need rebench here and we can merge. @XY-Wang can you send your wallet address?

[dmoka]

@XY-Wang Please adjust the failing test and bump the necessary versions, then we are good to go.

[XY-Wang]

Merged from master and fixed the failing test.

You can use the address 152n2TXMkYa2oLgNyDK1H7X7D3WFjoShVCSUBceATccjTzza.

Thanks and happy new year!

[XY-Wang]

Hi @dmoka, I fixed the formatting and bumped the versions that were causing the pipeline to fail. Please try to run it again, sorry for the inconvenience.

[XY-Wang]

@dmoka @jak-pan Could you please advise on how to merge this PR without failing the version checks? It seems that version updates from other merged branches are causing the committed version here to become outdated on each pipeline run.

[dmoka]

@XY-Wang Pls bump pallet-omnipool to v4.5.0, then we are good to go.