CAMEL-21917: Fix flaky JMS transacted and security tests

[gnodet]

Summary

Fix multiple flaky JMS transacted and security tests in camel-jms that were failing intermittently on CI (both JDK 21 and JDK 25).

Root Causes & Fixes

DLQ tests failing with null receive (JmsTransactedDeadLetterChannelNotHandlerRollbackOnExceptionIT, JmsTransactedDeadLetterChannelHandlerRollbackOnExceptionIT, JmsTransactedOnExceptionRollbackOnExceptionIT, JmsToJmsTransactedIT)

• Artemis does not auto-create dead letter queues for custom DLQ addresses without autoCreateDeadLetterResources. Fixed by pre-creating the DLQ queue in broker config via cfg.addQueueConfiguration(QueueConfiguration.of(dlqName).setRoutingType(RoutingType.ANYCAST))
• Use per-class DLQ names (DLQ.<ClassName>) to prevent interference between concurrent tests
• Set explicit maxDeliveryAttempts (1 or 3) per test for faster, deterministic redelivery

Message leakage between test methods (RouteIdTransactedIT, JmsToJmsTransactedIT)

• Tests sharing a broker queue could leak messages between methods when execution order was non-deterministic
• Fixed with @TestMethodOrder(MethodOrderer.OrderAnnotation.class) and @Order annotations

Timeout flakiness under CI load

• Increased Awaitility timeouts and @Timeout values in several tests that were too tight for CI

JDK 25 compatibility (JmsToJmsTransactedSecurityIT)

• Fixed Artemis security configuration to work on JDK 25

Files Changed (22 files)

Category	Files
DLQ test fixes	JmsTransactedDeadLetterChannelNotHandlerRollbackOnExceptionIT, JmsTransactedDeadLetterChannelHandlerRollbackOnExceptionIT, JmsTransactedOnExceptionRollbackOnExceptionIT
Transacted test fixes	JmsToJmsTransactedIT, RouteIdTransactedIT
Security test fix	JmsToJmsTransactedSecurityIT
Timeout increases	JmsProducerWithJMSHeaderTest, JmsRouteWithInOnlyAndMultipleAcksTest, JmsRouteWithInOnlyTest, AsyncConsumerInOutTwoTest, JmsAddAndRemoveRouteManagementIT, and others
Test infra	AbstractArtemisEmbeddedService

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.