Part 1,2,3,4 for issue #24900 Document and rename some ResourceHandle fields.

[escay]

Part 1 for issue #24900 Document and rename some ConnectionPool fields.
Remove some unused methods and constructor parameters. Functional / possible incompatibility changes in DataStructureFactory and in ResourceHandle due to constructor changes.

Part 2 for issue #24900 Start with a new PoolManagertImpl unit test to understand enlisted versus busy states of Resource handles and the wiring inside a transaction to keep track of all used resources.

Part 3 for issue #24900 More documentation and more unit test coverage.

Part 4 for issue #24900 Add more detailed logging to improve log file analysis.

[dmatej]

I have started the TCK run for this PR for sure.
https://ci.eclipse.org/jakartaee-tck/view/EFTL-Certification-Jobs-10/job/eftl-jakartaeetck-run-standalone/132/
https://ci.eclipse.org/jakartaee-tck/view/EFTL-Certification-Jobs-10/job/jakartaee-tck/job/10.0.x/144/

[dmatej]

Tests passed except several which were broken by yasson which contains JDK17 based classes unusable with JDK11. However we should merge this PR as nothing else broke.

Details about poisoned staging repo:

• The repo is ok now, I checked yasson for sure
• My computer was poisoned too, so it seems that around this date the yasson.jar in staging was broken:

  #NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice.
  #Wed Jul 24 22:13:51 CEST 2024
  yasson-3.0.4-javadoc.jar>staging=
  yasson-3.0.4-sources.jar>staging=
  yasson-3.0.4.jar>staging=
  yasson-3.0.4.pom>staging=
  

• yasson with the same version in Maven Central is compiled for Java 11, but this file used Java 17 and cannot be used with 11.
• GlassFish 7.0.17 contains correct version.