Ref #71 Jakarta migration

[f2par0]

fixes #71

Hello, this is an attempt to migrate to jakarta.

• moved to java 17
• updated pom version to 2.0.0-SNAPSHOT
• usage of test containers instead of embedded activemq/artemis to avoid conflicting javax dependencies

The biggest rock left is pax-jms-pool-tranx because pax-trans-jms doesn't have jakarta version yet either.

What is your opinion on it : migrate pax-trans-jmx to replace all geronimo dependencies to jakarta ?

[grgrzybek]

These should not be system packages.

[f2par0]

I haven't found another solutions to make it work with test container, try to add test containers bundle to the container, but never got it to work and PaxExam does not provide a way to do something outside of the container before the test. I've done something like this in camel-karaf, but here it just seemed simple to add this, unless you think there is a better solution.

[grgrzybek]

Thanks for the PR - I've added some comments in the review.

Do we really need .github/copilot-instructions.md? It contains contradictory statements from what you changed...

• JDK 11 vs 17
• OSGi Framework Felix 5 (ancient)
• DS annotations are good for applications, but not quite for libraries as this one
• There's no Artemis 3.0
• Write meaningful commit messages - when your commit messages are just attempt to fix integration tests - I don't like squashing commits, but two commits with the same message are not nice. Also commits should refer to an issue (like [#71])

[f2par0]

Thanks for the comments, I'll remove copilot instructions, they were not that useful anyway.
I squashed some commits, will do some cleanup when solution works completely

[f2par0]

Hello @grgrzybek , in order to restore transx feature, I created 2 PRs ops4j/org.ops4j.pax.transx#74 and apache/aries#790 to migrate them jakarta namespace as well