Remove standalone JSP TCK sources

[alwin-joseph]

Describe the change

• Removing the standalone pages TCK sources from platform TCK project.
• Add glassfish TCK runner for platform jsp tests
• 18 tests pass , 10 tests fails

Pending:

• 10 tests fail due to deployment failures , this seems to be configuration issue with the test runner ; will need to revisit the Create Custom Resource(myUrl) .

From server logs :

Exception while deploying the app [jsp_tagext_resource_taghandler_web] : JNDI lookup failed for the resource: Name: java:module/env/myUrl, Lookup: http://webServerHost:webServerPort, Type: java.net.URL -- Lookup failed for http://webServerHost:webServerPort in SerialContext[myEnv={java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}]]]

Additional context

• The standalone Pages TCK was migrated to specification repository at https://github.com/jakartaee/pages/tree/master/tck
• glassfish TCK runner for standalone pages tck was created in GlassFish runner for the Pages TCK #1324

[scottmarlow]

Has https://github.com/jakartaee/pages/tree/master/tck passed any testing with a Pages implementation?

[alwin-joseph]

Has https://github.com/jakartaee/pages/tree/master/tck passed any testing with a Pages implementation?

The Glassfish 8.0.0-M2 passed. I will wait for Tomcat to re-verify it (after the TCK was restaged) to move the PR out of draft.

pages Spec PR for ballot : jakartaee/specifications#723.
CCR for Tomcat 11 : jakartaee/pages#265.

[markt-asf]

Tomcat verified the re-staged TCK:
jakartaee/pages#271