Need to define how specification TCKs that reference other specification containers are handled

Nobody has claimed this yet.

**Is your feature request related to a problem? Please describe.**
We have a problem with circular dependencies in TCKs for specifications like CDI that in addition having a base Java SE behavior, define behaviors and have TCK tests for many other specification containers; EJBs, JMS, JPA, JTA, Servlet, etc.

**Describe the solution you'd like**
The CDI team is in the process of separating out the TCK tests into two sets; a Java SE base and a Web profile base. We need this separation of dependencies in general for specifications that are targeting the core profile and to break current circular dependencies in the overall release process as it relates to TCKs. A natural place for these separated TCK tests would be the lowest profile/platform that encompasses the required containers.

**Describe alternatives you've considered**
The specification projects could have separate TCK release artifacts that are extensions of the profile/platform TCK that are new standalone TCKs that need to be run as part of the profile/platform TCK.

**Additional context**
None

No files or tests are named. Start by reviewing the Jakarta EE Platform TCK and profile dependency process, including the proposed CDI Java SE and Web profile separation and standalone TCK alternative; done means defining a general handling model that breaks circular dependencies.

Written by the indexing model from the issue text.