TCK Tracking: Jakarta EE 10 Core Profile #6799

[jbescos]

Relates to #6799

Some TCK tests are excluded in restfull and cdi. You can see them with a <!-- FIXME: Next tests must be enabled --> in the pom file. I will create a new issue to address that.

URL of the TCKS:
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/promoted/eftl/

[jbescos]

This PR is ready for review.

[tomas-langer]

There are a few .sh files in the PR, with no explanation in a README.md or simillar - do we need those files? If we do, why and how should we use them?
Any shell script is a danger for us - we need to maintain them, and if called from aynwhere in maven (or ant that was added), it may do things that are unexpected.

[jbescos]

There are a few .sh files in the PR, with no explanation in a README.md or simillar - do we need those files? If we do, why and how should we use them? Any shell script is a danger for us - we need to maintain them, and if called from aynwhere in maven (or ant that was added), it may do things that are unexpected.

These sh and ant scripts exists because TCK artifacts don't exist in any maven repository. They submit a zip file with the jars, and sometimes there is an SH file to install dependencies.
In some zip files the SH file is missing. To be consistent with the other ZIPs, I created the missing SH scripts.

I think there is no need for READMEs because nobody is supposed to understand and execute that. They are executed as a part of the maven ant plugin.

[jbescos]

I added the readmes for the sh files

[jbescos]

TCK Inject failed because I changed the visibility of microprofile/tests/tck/tck-inject/tck-inject-test/src/test/java/io/helidon/microprofile/tests/inject/AtInjectTCKExtension.java from public to package.

I have deleted that class and loaded it from the one that exists in jakarta.inject-tck-2.0.2-bin.zip