Adding Jakarta Messaging 3.0 support

[samueleresca]

See: #483

Few notes regarding the PR after spending some time on this:

• Jakarta JMS 3.1 requires Java 11+, see Jakarta Messaging 3.1.0 Release Review. This PR is upgrading to Jakarta JMS 3.0 which is the latest release supporting Java 8.
• ActiveMQ Classic is used in the jms connector to perform the integration tests. ActiveMQ classic cannot be upgraded to a version later than 5.16.7 because the later versions don't support Java 8.
• ActiveMQ Classic 5.16.7 only supports Javax JMS 1.1.
• I replaced ActiveMQ Classic with ActiveMQ Artemis, which supports both the new versions of JMS and also Java 8. I wasn't able to port the following 2 tests using ActiveMQ Artemis:
  • JmsProducer should retry sending on network failures
  • The JMS Transactional Connectors ensure no message loss or starvation when exceptions occur in a stream missing commits

[pjfanning]

@samueleresca is this PR complete? I'm hoping to start a discussion about a Pekko Connectors 1.1.0-M1 release. This can be delayed until after that release if that suits you better.

[samueleresca]

@samueleresca is this PR complete? I'm hoping to start a discussion about a Pekko Connectors 1.1.0-M1 release. This can be delayed until after that release if that suits you better.

There is a comment @laglangyue that I need to address, apart from that it is ready. It would be great to merge this for Pekko Connectors 1.1.0-M1.

[pjfanning]

@samueleresca This is the last PR blocking the release. Again, I'm happy to move on with the M1 release without this and to have it merged prior to the full 1.1.0 release.

[samueleresca]

@samueleresca This is the last PR blocking the release. Again, I'm happy to move on with the M1 release without this and to have it merged prior to the full 1.1.0 release.

@pjfanning The PR is ready apart few minor comments that I think shouldn't block the merge. So I'm happy to get the approval and get this merged