Add tests for Jakarta EE integration of Jakarta Persistence with the CDI bean manager

[scottmarlow]

Add tests for jakartaee/platform#746

[edburns]

Notes from Platform call

• Stateless session beans have always been challenging to test robustly.
  • JPA 2.1 clarification: when you use EntityManager outside of a transaction, after each entity call, the PersistenceContext state is not preserved.

[scottmarlow]

Notes from Platform call

* Stateless session beans have always been challenging to test robustly.
  
  * JPA 2.1 clarification: when you use `EntityManager` outside of a transaction, after each entity call, the `PersistenceContext` state is not preserved.

Unless a persistence unit hint (e.g. extension) like jboss.as.jpa.deferdetach is used to defer the clearing/close of the persistence context until the session bean call completes.

[edburns]

Depends on #1624 .

[jhanders34]

The first testing for this issue only includes EntityManager. @Inject also needs to be tested with EntityManagerFactory, CriteriaBuilder, Cache, Metamodel, SchemaManager and PersistenceUnitUtil as was just presented at JakartaOne by Gavin King.

[starksm64]

https://in.relation.to/2024/08/20/cdi-jpa/

[arjantijms]

With #1686 and #1687, all the functionality is tested, although it a very crude way (just that the artefacts are indeed injected).

[edburns]

From 2024-12-10 Platform call:

PRs merged include qualifier scenarios, but doesn’t actually use the artifacts that are injected to make sure that they are the right injected instances for the qualifiers. The test just validates that injection happens, but not the content of the injected value.
Custom scope testing is not included yet.