Added GlassFish's bootstrap modulepath

[dmatej]

• Will come with Glassfish 7.1.0

Related Issue(s)

• With this branch of the TCK this PR slowly passes all TCK tests for future GlassFish 7.1.0, see Redesign of GlassFish bootstrap eclipse-ee4j/glassfish#25183 and Late Christmas Present - GlassFish 7.1.0 eclipse-ee4j/glassfish#25225
• It should not break also older GlassFish builds, I will recheck later.

Describe the change

• Especially appclient based tests explicitly use Glassfish classes to run the client, they have to specify classpath, required system options, etc - and also modulepath introduced in JDK11 but not used until GlassFish 7.1.0.
• The bootstrap module path contains several jar files between JDK and GlassFish and it is fully JPMS enabled.

Additional Context

• The classpath of the appclient could be simplified in the TCK just like in GlassFish 7.1.0, however I doubt anyone would like to spend time with that for this TCK version.
• I am slowly running TCK tests for the future GF 7.1.0-SNAPSHOT, currently it locally passes ejb32 and persistence.
• I am waiting for a new hardware, then verifying all tests against two GF versions (7.0.20 and 7.1.0-SNAPSHOT) should be a thing of one or two days.

CC @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @OndroMih @dmatej
@starksm64 @scottmarlow