Setup Jakarta Messaging 3.1 TCK

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.

Start by locating the existing ActiveMQ test profiles and GitHub workflow configuration, then determine where the Jakarta Messaging 3.1 TCK can be integrated without affecting normal runs. Done means the TCK is runnable on demand through a dedicated profile or GitHub workflow and provides a clear compatibility assessment.

Written by the indexing model from the issue text.