Create guidance on how to produce standalone TCKs

**Is your feature request related to a problem? Please describe.**
We have a mix of testing technologies that don't mix well together to enable a collection of standalone TCKs that can be composed to produce various profile level TCKs. We need to provide guidance on how to achieve this.

**Describe the solution you'd like**
The specification project should own the TCK source and produce the TCK artifacts. This needs to be done in such a way that the artifacts can be run to validate implementations at the individual specification level, as well as integrated into platform level TCKs.

**Describe alternatives you've considered**
Jakarta Batch, Bean Validation and CDI make use of TestNG and Arquillian with maven artifacts to enable composition. Ondro Mihályi looked at this approach and also Junit 5 in the context of Jakarta Batch.

**Additional context**
An investigation of using TestNG/Arquillian and Junit 5 to update the Jakarta Batch TCK was described in this blog by Ondro Mihályi:
https://ondro.inginea.eu/index.php/possible-ways-to-use-arquillian-in-jakarta-ee-tcks/

Start by reviewing the issue requirements and Ondro Mihályi’s linked investigation of TestNG/Arquillian and JUnit 5 for Jakarta Batch. Compare the approaches used by Jakarta Batch, Bean Validation, and CDI. Done means documented guidance for producing standalone TCK artifacts that validate individual specifications and compose into platform-level TCKs.

Written by the indexing model from the issue text.