Automate AQAvit tagging and release branch creation

[smlambert]

Update and move the scripts from https://github.com/smlambert/release-aqavit/tree/main/scripts into aqa-tests repo and create a workflow for this process. Workflow can be manually run for now, but can consider adding a schedule where we run it 7 weeks before an OpenJDK release (as per this schedule).

Expected behaviour of automation:

• For CPU, we tag and create release branches based from the expected tags defined here

• For Feature releases and respins, we have tended to tag and create a release branch, then use that same AQAvit release branch for the CPU directly following it (March/April and Sept/Oct share release branches, and only if needed, branched a dot release from it, so if March 2024 JDK 22 was v1.0.1-release branch, then April 2024 CPU would see the update of JDK22 and addition of JDK8, JDK11, JDK17 and JDK21 information into the testenv.properties of the v1.0.1-release branch. If a breaking change was required in the branch, then create a separate branch named v1.0.1.1-release derived from the v1.0.1-release branch would be created and used for a CPU release (or a respin of a CPU or feature release). This seems to have served us well, so continue in this fashion for now.

[smlambert]

For this immediate generation of tags and aqa-tests release repo, I will not worry about putting a workflow in place, but rather just check that the updated scripts work satisfactorily.

From java.com/releases, "22.0.1, 21.0.3, 17.0.11, 11.0.23, 8u411" are the JDK tag prefixes targeted for April and "22.0.0" ? for March, so I will use "22.0.0-ga, 21.0.3-ga, 17.0.11-ga, 11.0.23-ga, 8u411-ga" and after March release activities complete, will update testenv.properties file to 22.0.1-ga prefix. In this way, we will plan to leverage same release branch for March and April.

[smlambert]

Rather than move this into aqa-tests, I propose we create a new repo called aqavit-release-scripts (where we can also add scripts for gathering metrics on releases) we put the aqavit release scripts into github-release-scripts repo (only caveat, but not a showstopper is that that repo is currently listed under the Temurin project developer resources). Metrics will be moved into a new repo as per #5121 (comment).

[smlambert]

I will transfer this issue to github-release-scripts to complete the work over there. Because github-release-scripts is under the Temurin project, where many of the AQAvit committers do not have commit rights, I will move this back to the aqa-tests repo.