Fixes: nomenclature confusion in XCM tests

[xeodus]

Refactor XCM Nomenclature

This PR resolves confusing naming conventions in XCM emulator tests. The key changes address a common pain point where runtime implementations were incorrectly named "pallets" in macro-generate code.

Core Changes

• Renamed [<$name ParaPallet>] to [<$name ParaRuntime>] in decl_test_parachains! macro
• Fixed the naming confusion in XCM emulator tests from <Rococo as RococoPallet>::XcmPallet::force_xcm_version to <Rococo as RococoRuntime>::XcmPallet::force_xcm_version
• Documentation for how the decl_test_parachains macro works with emulated chains for both substrate devs and internal developers

[acatangiu]

Not sure if this rename is worth it as it introduces a lot of changes everywhere it's used: all runtime tests. It will require the name changes to https://github.com/polkadot-fellows/runtimes/ too.

It introduces a lot of noise (changes) for not much reason. I would not do it.

Even so, @xeodus if you insist on it and want to spend the time doing it all the way, I will not block it. You can start by making all emulated tests compile/pass to get an idea of all the required changes.

cargo test -p asset-hub-rococo-integration-tests -p asset-hub-westend-integration-tests -p bridge-hub-rococo-integration-tests -p bridge-hub-westend-integration-tests -p collectives-westend-integration-tests -p coretime-rococo-integration-tests -p coretime-westend-integration-tests -p people-rococo-integration-tests -p people-westend-integration-tests

[bkontur]

Not sure if this rename is worth it as it introduces a lot of changes everywhere it's used: all runtime tests. It will require the name changes to https://github.com/polkadot-fellows/runtimes/ too.

It introduces a lot of noise (changes) for not much reason. I would not do it.

Even so, @xeodus if you insist on it and want to spend the time doing it all the way, I will not block it. You can start by making all emulated tests compile/pass to get an idea of all the required changes.

cargo test -p asset-hub-rococo-integration-tests -p asset-hub-westend-integration-tests -p bridge-hub-rococo-integration-tests -p bridge-hub-westend-integration-tests -p collectives-westend-integration-tests -p coretime-rococo-integration-tests -p coretime-westend-integration-tests -p people-rococo-integration-tests -p people-westend-integration-tests

Exactly 👆

@xeodus I see you basically picked this #2416 issue.

If you want to help with integration emulated tests, maybe much more useful/helpful would be de-duplicate and simplify existing tests themself, so we could easier maintain and/or reuse for polkadot-fellows also.

Or check/verify something from these:
#1127 (not sure if it is still an issue)
#2460 (not sure if it is still an issue)
paritytech/roadmap#50 (here several other related issues to check)

[acatangiu]

Please re-open if you plan on continuing, but after you get the tests compiling locally:

cargo test -p asset-hub-rococo-integration-tests -p asset-hub-westend-integration-tests -p bridge-hub-rococo-integration-tests -p bridge-hub-westend-integration-tests -p collectives-westend-integration-tests -p coretime-rococo-integration-tests -p coretime-westend-integration-tests -p people-rococo-integration-tests -p people-westend-integration-tests