TCK: old-tck/run/pom.xml appears to be hardwired to glassfish

**Challenged tests**
Everything under old-tck/run seems to be hardwired to depend on glassfish.

**TCK Version**
Jakarta Faces TCK 4.1.1

**Description**
old-tck/run/pom.xml includes hardwired dependencies and references to files in a glassfish distribuion.

**Additional context**
Are we allowed to change the pom?

Start by reading old-tck/run/pom.xml and listing its hardwired GlassFish dependencies and references to distribution files. Clarify whether the POM may be changed and what runtime or dependency setup the challenged tests should support; done means the tests no longer depend on an unintended GlassFish-specific configuration.

Written by the indexing model from the issue text.