WIP: Converting tck remote execution code to launch them seperately

[adamfarley]

For the sake of status tracking. Will be later supported by a change to separate the different remote job executions into different pipeline stages.

Resolves #1303

[github-actions[bot]]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR. If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here. To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

[adamfarley]

Rerunning test to verify recent changes: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk21u/job/jdk21u-linux-x64-temurin/379/

Update: Smoke test failed due to the absence of make and weston.

Raised an issue here: https://github.com/adoptium/infrastructure/issues/4138

That doesn't appear to be related to this PR, so I'm rerunning the test.

https://ci.adoptium.net/job/build-scripts/job/openjdk21-pipeline/427/