Create and trial an agentic workflow to triage release issues

To shift some of the release triage work to agents, we would like to trial an agentic workflow to do the following:

- Look at each JDK version that has a central triage issue named with the following 'Month Year Release AQAvit Activities' and several related issues (for each platform covered in that version, named like this 'Triage Automated Tests for Month Year JDKxx - platform').
- If the central triage issue has a Jenkins pipeline link in its description, then edit the description of the related 'Triage' issues with the links to the instances Jenkins child jobs (called AQA_Test_Pipeline_JCK and AQA_Test_Pipeline_RELEASE) for that platform.
- The agent can query TRSS and Jenkins to gather information about the various sub-jobs and deep history and how testcases behave across platforms (see related TRSS queries to gather this).
- Use this documentation to help know what info to gather and what are the next best recommended actions to take: https://github.com/adoptium/aqa-tests/blob/master/docs/pages/Triage.md#triage-guidance and https://github.com/adoptium/aqa-tests/blob/master/docs/pages/TriageChecklist.md

Start with docs/pages/Triage.md#triage-guidance and docs/pages/TriageChecklist.md, then review the central and related issue naming patterns described here. Trial the workflow against release issues with Jenkins pipeline links, gathering the specified Jenkins and TRSS information; done means related issue descriptions contain the platform child-job links and the workflow recommends next actions.

Written by the indexing model from the issue text.