Setup Jakarta Messaging 3.1 TCK

[jeanouii]

We need to setup Jakarta 3.1 TCK on Apache ActiveMQ
It needs to be activated only on demand (specific profile because it takes a bit of time to run). We'll probably create a dedicated run on Github to run those.

Quoting JB on the email thread discussion.

It is great to have this for two main reasons:

1. It provides a clear assessment of our current Jakarta Messaging 3.1 support and identifies the remaining gaps.
2. It gives us the opportunity to be listed as a compatible implementation on the Jakarta website.

[jeanouii]

Known Failures

The majority of failures are caused by unimplemented JMS 2.0 features in ActiveMQ:

Category	Root Cause	Failures
Async send	CompletionListener APIs throw UnsupportedOperationException	36
Shared subscriptions	createSharedConsumer / createSharedDurableConsumer not implemented	12
receiveBody()	JMSConsumer.receiveBody(Class<T>) not implemented	12
Delivery delay	setDeliveryDelay / getDeliveryDelay not implemented	10
JMS version metadata	ConnectionMetaData reports version 1.1 instead of 3.1	4
Exception types	Wrong exception class thrown in several edge cases	~15
Other	Temp destination lifecycle, property handling, security exceptions	~12