Platform-specific reproducibility healthcheck

[adamfarley]

This change allows us to identify the latest build of a specific tagged jdk source version per platform.

Previously, we would gather results from the oldest build pipeline using a specific tagged source version.

This change allows us to re-run specific platforms, and have the latest build override the first one, while still using the builds from the original pipeline for other platforms.

This change also includes making all of our wget calls more robust, in case we use invalid key parameters for the trss api and become hung.

Resolves #1132

[github-actions]

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]

This code has been tested, and here is the output:

Note that the Linux x64 "?%" output is correct, as the test failed to produce a valid percentage.

[adamfarley]

Thanks @andrew-m-leonard and @karianna 🤓