Support generation of "release" pipeline and build jobs for "release build Tag" support

[andrew-m-leonard]

The new "build ref tag" support for releases needs an extension to the generation build job to support generating a "Release" pipeline and build jobs based off the given "build-ref's" (temurin-build, ci-jenkins-pipeline, helper). So you would manually run the generation jobs with an option "Build-ref tag: xxx". Which then generates, eg:

• release-openjdk17-pipeline
• release-jobs/jdk17u/jdk17u-aix-ppc-..., .....

[zdtsw]

so to understand the requirement of this issue:

when it comes to an official CPU/release,

1. we should create tags in temurin-build, ci-jenkins-pipeline and jenkins-helper 3 repos. with exactly the same tag name.
2. we run the new release-build-pipeling-generator jenkins job(s), with above tag as input, which in turn, create

• pipelines/downstream jobs (if not exist for the jdk version yet)
• re-generate pipelines/downstream jobs (already ones from previous release)

dedicated for official CPU/release purpose

They should be placed in and named like

• under the folder: https://ci.adoptopenjdk.net/job/build-scripts/ release-openjdkX-pipeline
• under the folder: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/release/job/jobs/ jdkX-release-****

The goal of this issue is to implement this auto-generation release-build-pipeling-generator pipeline

[zdtsw]

Ref #495 and adoptium/temurin-build#3155

[zdtsw]

As long as we define the tag's name, we can make the new release-build-pipeling-generator job based on

Refspec: '+refs/tags/v*:refs/remotes/origin/tags/v*'
Branch Specifier: **/tags/v** 

to create these release pipeline/jobs

but maybe it is good to just manual trigger it for now, more safe to know and see the job runs by release champion