Update Daily Slack EA status to report published EA Test job failure & testcase stats

[andrew-m-leonard]

• Make the published EA build status also report "AQA test failures: TestJobs=N/Tot TestTargets=N/Tot."
  To highlight need to fix/exclude to failures.
• Also correct reproducibility% status which is currently incorrectly reporting and not finding the relevant reproducible build test

Example output: https://adoptium.slack.com/archives/C09NW3L2J/p1738669436392289

[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"

[smlambert]

I have not looked at it closely, but want to make sure we are using correct nomenclature, if you are pulling info from TRSS, you are likely pulling test target information, not testcase information, will look more closely when back at my desk

[andrew-m-leonard]

I have not looked at it closely, but want to make sure we are using correct nomenclature, if you are pulling info from TRSS, you are likely pulling test target information, not testcase information, will look more closely when back at my desk

Yes you're right, i'll change text to "TestTarget"

[andrew-m-leonard]

I have not looked at it closely, but want to make sure we are using correct nomenclature, if you are pulling info from TRSS, you are likely pulling test target information, not testcase information, will look more closely when back at my desk

That terminology has been wrong for a while... i've corrected all the existing instances too.

[andrew-m-leonard]

@smlambert I've ended up fixing quite a bit in this PR with some re-factoring!, including the reproducibility% which was incorrectly searching for the ReproducibilityTest hence why it was not reporting anything...
If you could specifically review these sections please:

• getPipelineTestResults
• getFailedTestSummary
• Summary text sequence

[smlambert]

thanks @andrew-m-leonard !