Bridges testing improvements

[bkontur]

This is a global summary issue for all testing-related matters concerning Bridges. (all issues will be re-visited and adjusted)

Runtime testing

• https://github.com/paritytech/parity-bridges-common/issues/2612
• https://github.com/paritytech/parity-bridges-common/issues/2579
• https://github.com/paritytech/parity-bridges-common/issues/2453
• https://github.com/paritytech/polkadot-sdk/issues/5708
• https://github.com/paritytech/polkadot-sdk/issues/5552

Live testing (for testnet)

• https://github.com/paritytech/parity-bridges-common/issues/2640

Integration-tests - xcm-emulator related

• https://github.com/paritytech/parity-bridges-common/issues/2849
• ? https://github.com/paritytech/parity-bridges-common/issues/2610

Chopsticks support

• https://github.com/paritytech/polkadot-sdk/issues/4793
• https://github.com/paritytech/polkadot-sdk/issues/3522
• https://github.com/AcalaNetwork/chopsticks/issues/681
• https://github.com/AcalaNetwork/chopsticks/pull/695
• https://github.com/AcalaNetwork/chopsticks/issues/741
• https://github.com/paritytech/parity-bridges-common/issues/2953

Others

• How to enable easier integration/e2e testing for parachains which want to use P<>K bridge?

[bkontur]

@serban300 @franciscoaguirre I think the dry-run and Chopsticks way has the same common problem, because there could possibly be DescendOrigin added here when dispatching on bridged chain. So, if we need to add some runtime api or whatever for that, it should cover both cases.