Switch to jakarta annotations

[jdpgrailsdev]

What

• Switch to Jakarta annotations package to avoid licensing/trademark issues.

How

• javax.inject -> jakarta.inject for Singleton, Inject and Named annotations.

More Details

Micronaut states the following with regards to the two packages:

Due to trademark restrictions imposed on the javax.* namespace, the Micronaut framework has switched from the javax.inject to the jakarta.inject annotations as the set of annotations that’s included by default with the Framework. We recommend that you switch your application to the new annotations. It should only be a matter of changing the imports. For current uses of javax.inject.Provider, we recommend switching to io.micronaut.context.BeanProvider.

This is based off of Oracle's trademark of the javax package space:

Oracle's Java trademarks are the property of Oracle and the Eclipse Foundation has no rights to use them. The implications of this are as follows:

1. The javax package namespace may be used within Jakarta EE specifications but may be used "as is" only. No modification to the javax package namespace is permitted within Jakarta EE component specifications. Jakarta EE specifications that continue to use the javax package namespace must remain TCK compatible with the corresponding Java EE specifications.
2. Jakarta EE component specifications using the javax package namespace may be omitted entirely from future Jakarta EE Platform specifications.
3. Specification names must be changed from a "Java EE" naming convention to a "Jakarta EE" naming convention. This includes acronyms such as EJB, JPA or JAX-RS.

Tests

• Project builds locally/all unit tests pass
• Project runs locally via docker-compose
• Connector created and sync successfully executed via local instance