chore(ci): deactivate DMQ node in release networks

[jpraynaud]

Content

This PR includes the deactivation of the DMQ node in the release networks until a stable 0.7.X is released:

• This will unlock the delivery of the next distribution
• Once the 0.7.0 version is released, the activation of the DMQ network can be done by merging the PR feat: upgrade DMQ node to 0.7.0.0 #3361 and following upgrade instructions in it.

Pre-submit checklist

• Branch
  • Commit sequence broadly makes sense
  • Key commits have useful messages
• PR
  • All check jobs of the CI have succeeded
  • Self-reviewed the diff
  • Useful pull request description
  • Reviewer requested

Issue(s)

Relates to #3271

[github-actions]

Test Results

     5 files  ± 0     209 suites  ±0   59m 28s ⏱️ - 19m 55s
 3 325 tests  - 20   3 325 ✅  - 20  0 💤 ±0  0 ❌ ±0 
11 070 runs   - 26  11 070 ✅  - 26  0 💤 ±0  0 ❌ ±0 

Results for commit b520482. ± Comparison against base commit 3254f5d.

♻️ This comment has been updated with latest results.

[Copilot]

Pull request overview

This PR temporarily disables the DMQ/P2P setup for the release environments (release-preprod and release-mainnet) so releases can proceed while waiting for a stable DMQ 0.7.X rollout.

Changes:

• Removed dmq-minimum-version for the mainnet and preprod entries in networks.json so DMQ compatibility for release networks becomes “N/A” in generated compatibility output.
• Disabled P2P/DMQ-related deployment flags for release-preprod and release-mainnet in the release workflow matrix.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
networks.json	Removes DMQ minimum version metadata for release networks, effectively marking DMQ as not applicable there.
.github/workflows/release.yml	Turns off P2P/DMQ flags for release deployments to prevent DMQ node usage in release networks.