chore(camel-test-infra-ibmmq): upgrade ibm.mq.container to 10.0.0.0-r2

[github-actions]

This PR updates the ibm.mq.container container image to version 10.0.0.0-r2.

Update Details

• Property: ibm.mq.container
• Image: icr.io/ibm-messaging/mq
• File: /home/runner/work/camel/camel/test-infra/camel-test-infra-ibmmq/src/main/resources/org/apache/camel/test/infra/ibmmq/services/container.properties
• Old version: 9.4.5.0-r2
• New version: 10.0.0.0-r2

Verification

Please verify:

• Container image version is compatible with existing tests
• No breaking changes in the updated version
• Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-ibmmq

Then test the impacted components.

---

This PR was automatically created by the Container Version Upgrade workflow.

[gnodet]

Claude Code review on behalf of @gnodet

LGTM — Approved. Automated container upgrade: IBM MQ 9.4.5.0-r2 → 10.0.0.0-r2. Major version bump — should be coordinated with the client library upgrade in PR #24040 (9.4.5.1 → 10.0.0.0). Pending CI validation.

[oscerd]

Dependency/container bump review — verified and approved:

• ibm.mq.container: icr.io/ibm-messaging/mq 9.4.5.0-r2 → 10.0.0.0-r2 in test-infra/camel-test-infra-ibmmq/.../container.properties.
• Registry is icr.io (project convention: no Docker Hub images) — unchanged, correct.
• Both generated metadata files (catalog/camel-catalog/.../test-infra/metadata.json and test-infra/camel-test-infra-all/.../metadata.json) are regenerated consistently with the new serviceVersion.
• Blast radius is test-infra only (integration tests); no production code touched.
• Consistent with the open dependabot bump of the matching client library com.ibm.mq:com.ibm.mq.jakarta.client 9.4.5.1 → 10.0.0.0 (#24040) — the MQ 10 move is coherent across image and client. Worth merging both in the same window so the IBM MQ integration tests exercise client and broker at the same major version.
• Note: this is a major-version bump of the broker image (9 → 10); if the IBM MQ integration tests aren't part of PR CI, a local mvn verify -Pit run in components/camel-jms/ibmmq-related modules before the next release would be a cheap sanity check.

Reviewed with Claude Code (Fable 5) on behalf of oscerd. This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.

[gnodet]

Claude Code on behalf of gnodet

✅ Approved — Container upgrade verified. No regressions detected.

Test Summary

The IBM MQ container upgrade from 9.4.5.0-r2 to 10.0.0.0-r2 was tested locally. The two IBM MQ-specific tests (JmsComponentIbmMQTest and JmsReplyToIbmMQTest) fail on this test server with a 30s JMS connection timeout — however, the same tests also fail with the old 9.4.5.0-r2 image on this server (identical ConditionTimeoutException). This is a pre-existing environment limitation (the server is too slow for IBM MQ's heavy container within the 30s Awaitility timeout), not a regression introduced by this upgrade.

The container starts correctly, the queue manager initializes, and the listener binds — it's purely a startup timing issue on resource-constrained hardware.

Change scope: Only container.properties is modified (version bump), no code changes — minimal risk.