XCM over bridges DX/UX - testing, tracking, examples, documentation

[acatangiu]

High-level tracking issue for improving XCM over bridges DX/UX:

Polkadot<>Kusama bridge:

• Support testing with Chopsticks
  • Bridges: enable chopsticks to emulate passing XCM messages over bridge #4793
• Support XCM dry-running
  • dry_run_xcm support for BridgeHubs #5708
  • Dry run xcms on bridge hubs to get forwarded xcms across the W<>R bridge #6002
  • [P<>K bridge] Support dry-running XCM over bridge polkadot-fellows/runtimes#477
• Support easy offchain tracking
  • Improve the runtime release process to include debug wasm in artifacts polkadot-fellows/runtimes#268
  • Replace log with tracing on Bridge-related modules #9279
  • Replace log with tracing on bridge-runtime-common #9288
  • Replace log with tracing on pallet-bridge-grandpa #9294
  • Replace log with tracing on pallet-bridge-messages #9308
  • Replace log with tracing on pallet-bridge-parachains #9318
• Add PET tests to cover CUJs and all the above
  • Bridges: enable chopsticks to emulate passing XCM messages over bridge #4793
• Add guide(s) for CUJs (including offchain tracking)
  • for end-users we can include example UIs to use (e.g. Turtle)
  • for dapps/builders we testing/building guide and reference PETs for specific CUJs

CUJs:

• todo

[acatangiu]

Some work started here: #6002

[acatangiu]

polkadot-fellows/runtimes#477