Automate AQAvit tagging and release branch creation

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](https://www.java.com/releases/)).

Expected behaviour of automation:
- For CPU, we tag and create release branches based from the expected tags defined [here](https://www.java.com/releases/)

- 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](https://github.com/adoptium/aqa-tests/tree/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.