Enhancements to early access build publishing

[sxa]

Follow-on to https://github.com/adoptium/temurin-build/issues/3355 to solicit ideas and track progress for further enhancing our distribution of early access builds.

Some ideas:

• Move to publishing tagged early access builds instead of nightlies for all releases, not just JDK21
• Try to include evaluation pipelines in the published output when they work (There were failures in some those builds which are being addressed) - it's currently a "fire and forget" in the background that doesn't affect the status of the trigger job
• The current trigger job is very much a WIP and could use some tweaks (or a complete re-write into a proper version controlled pipeline...)
• We've set some of the process because it was the minimal viable changes to make publishing of the releases with suitable naming work. It would likely be preferable to enhance the release tool to have some extra code for these tagged EA builds. See the comment in the previous issue regarding why we've used "ea_21-0-22` as a format for the filenames.
• Adjust the job so it can publish automatically with a suitable name instead of having to use "Nightly without publish" and publish separately
• Related to the above, the evaluation pipelines are not automatically published and require a re-run of the release tool with the appropriate upstream job name/number pointing at a run of evaluation-openjdk21-pipeline because they're currently a "fire and forget" in the background when they're kicked off
• See if there is a preferable format for the version string - this is what it is just now:

openjdk version "21-beta" 2023-09-19
OpenJDK Runtime Environment Temurin-21+34-202308040331 (build 21-beta+34-202308040331)
OpenJDK 64-Bit Server VM Temurin-21+34-202308040331 (build 21-beta+34-202308040331, mixed mode, sharing)

[sxa]

External references:

• Upstream OpenJDK EA releases of 21
• Azul EA releases of 21