Extend daily Slack build status with remote test job status

[andrew-m-leonard]

Currently the daily Slack build & test status script: https://github.com/adoptium/ci-jenkins-pipelines/blob/master/tools/nightly_build_and_test_stats.groovy
reports the build and AQA tests run/success status eg: https://adoptium.slack.com/archives/C09NW3L2J/p1783247625961719

jdk11u EA: Healthy. Build: [jdk-11.0.32+7-ea-beta](https://github.com/adoptium/temurin11-binaries/releases/jdk-11.0.32%2B7-ea-beta).
AQA test failures: TestJobs=4/279 TestTargets=78/3036.

It would be useful to report "RemoteTargets" (aka 'jck'), so we could have something like (note this is reporting the number of failures... so 3 failed out of 32 remote 'jck' targets):

AQA test failures: TestJobs=4/279 TestTargets=78/3036 RemoteTargets=3/32.

TRSS API now supports getRemoteJckBuildInfo eg.

curl -o trss.out -L "https://trss.adoptium.net/api/getRemoteJckBuildInfo?url=https://ci.adoptium.net&buildName=AQA_Test_Pipeline_JCK&buildNum=372"

[Akshat005Chaudhary]

@andrew-m-leonard @smlambert I've picked this up and put together a fix in this PR.

The implementation calls the TRSS getRemoteJckBuildInfo API for any AQA_Test_Pipeline_JCK child build found within the pipeline, accumulates the failed/total remote target counts, and appends RemoteTargets=X/Y to the Slack message. If no JCK build is present for a release, the field is simply omitted so existing output is unchanged.

Would appreciate a review, particularly to confirm the buildName pattern AQA_Test_Pipeline_JCK is the right string to match against in the TRSS child builds, and whether UNSTABLE should count as a failure for RemoteTargets or be treated separately.

[andrew-m-leonard]

@Akshat005Chaudhary thank you for taking a look, however someone on our team is already looking at this, thanks

[samyoon20]

@andrew-m-leonard commenting!

[andrew-m-leonard]

@Akshat005Chaudhary I would just add it is always worth requesting ownership of an issue before starting work on an item, as this prevents duplication of effort.

[Akshat005Chaudhary]

@andrew-m-leonard oh no...