Delete the jersey-tck sub-project from this project

[jamezp]

This project includes a TCK runner for Jersey in the jersey-tck sub-project. It looks like it will always require a custom build of Jersey and a custom build of Glassfish to get the TCK to work. I think we should simply just remove this as it seems to serve no purpose for the project. If Jersey needs to run the TCK they can always create their own runner or simply use https://github.com/jakartaee/platform-tck/tree/main/glassfish-runner/rest-tck.

This just seems like cruft we need to maintain for no real gain.

[mkarg]

I added that long time ago when setting up the tck folder originally, to try out our initial tck tests with Jersey, and as a copy-paste template for vendors to get started.

I agree to removing it, but it would be cool if in turn vendors would post publicly how to easily run tck tests against their own products.

[jamezp]

It definitely made sense to me why it was there. I just couldn't get it to work because of the OSGi dependencies.

The RESTEasy TCK Runner uses WildFly and is pretty simple to use. When I get some time I'll try to document it better. It would require a SNAPSHOT build of RESTEasy, but that seems reasonable to me.