AssetHubNext Westend cleanup on ahm-tests branch

[karolk91]

Some cleanup around assetHubNext is required on ahm-tests as a follow up of merge of #210

• *.ts files that use name assetHubNext should use assetHubNextWestend
• snapshots corresponding to above must be renamed
• .ts and snapshots should be moved to Westend directory
• Github issues for notifications purposes must be created per Westend related network currently in use (Collectives, AssetHubNext)
• merge Westend related tests to master,
• ahm-tests should keep only changes that alter current master tests behavior that will become valid only after migration

[karolk91]

I will cover all the topics mentioned in this issue

[rockbmb]

One comment - it might only make sense to merge all changes to master after the migration is run on Westend.

Until then, the ported E2E test suites for Westend's AH should remain in ahm-tests; otherwise those will always fail due to the absence of some required features in the current Westend's AH runtime e.g. scheduler, staking, nomination pools, referenda, etc.

[karolk91]

One comment - it might only make sense to merge all changes to master after the migration is run on Westend.

Until then, the ported E2E test suites for Westend's AH should remain in ahm-tests; otherwise those will always fail due to the absence of some required features in the current Westend's AH runtime e.g. scheduler, staking, nomination pools, referenda, etc.

I actually had in mind that we could already merge the changes related to "Westend Asset Hub Next" (the chain under RPC: westend-asset-hub-next-rpc.parity-chains-scw.parity.io). But I learned shortly after that this chain will be decomissioned soon and we shouldn't really invest in having any test coverage for it

Totally agree, that anything that alters Westend Asset Hub (westend-asset-hub-rpc.polkadot.io) can only be merged after migration is done

[rockbmb]

@karolk91 closing this, let me know if still needed.