Investigate enhancement of remote trigger rerun feature

[smlambert]

We added the ability to rerun an entire dev.jck test job on the remote server (via #1235).
Now we would like to explore whether it is possible to remotely trigger a rerun of the 'automated _rerun' child jobs of the initially triggered dev.jck jobs. This would reduce the amount of resource and time spent on the TC server.

Various approaches to this problem, 2 that come to mind are:

1. Think this feature would entail a query to the initial dev.jck job for the Build ID of its child dev.jck...._rerun job. We could then potentially remotely trigger the child job (without visibility of the parameters of that job).

2. Another approach would be to set RERUN_ITERATIONS=2 or more, instead of 1, https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy#L718, which could be a stand in for certain types of intermittent failures. This approach should only be done once the dev.jck jobs are stabilized for all platforms. Noting that need to verify the default behaviour, believe it is, if the 1st rerun passes, the pipeline does not try to rerun again.