Add support for the latest environments (add devnet, retire summit/w3s)

[UtkarshBhardwaj007]

Summary

Add support for the latest environments: add the new devnet preset, retire the removed summit / w3s environment, and keep the paseo naming unambiguous.

Background

The environment set changed. The summit environment was removed, and a new devnet preset was added. The reference for the exact values is contract-dependency-manager PR #61 (paritytech/contract-dependency-manager#61).

Key facts from that change:

• devnet: the public products devnet on the Paseo testnet Asset Hub (para 1000, EVM chain id 420420417), wired to the community operated ContractRegistry at 0x59b0245778917af55224e5f8fb55f7f8d452619f. It uses the devnet-asset-hub / devnet-bulletin descriptors, the Bulletin RPC wss://bulletin-paseo.tservices.es:8443, and getChainAPI("devnet").
• summit / w3s: removed upstream. Anything selecting summit or w3s needs to move off it.
• paseo: the paseo preset targets paseo-next (para 1500), not the Paseo testnet.

What needs to happen

• Add devnet as a selectable network using the devnet-asset-hub / devnet-bulletin descriptors and getChainAPI("devnet").
• Update cdm.json to include the devnet registry and drop summit.
• Confirm the statement store matchmaking still works against the devnet Bulletin RPC.
• Remove any summit / w3s option and keep the paseo option labelled as paseo-next.

Acceptance criteria

• A full game round works on devnet, including the contract calls and statement store matchmaking.
• No summit / w3s option remains.
• Network labels are unambiguous.

[illegalcall]

Can i get assigned to it @UtkarshBhardwaj007 ?