Create new jobs to handle running Solaris builds via a Linux proxy machine

[sxa]

This issue covers the implementation of what was discussed in adoptium/infrastructure#3742 (comment)

Current status: Prototype jobs have been created for x64 and SPARC at:

• https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-x64-temurin-simple
• https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-sparcv9-temurin-simple

These are currently connecting to the target machine as the vagrant user (even on SPARC where I've created a user with that name for consistency). Note that the final solution should not use the vagrant user as that has sudo access on the "real" vagrant VMs.

These jobs are currently running with a post-build trigger of the corresponding test jobs described in #4099

Equivalent release jobs will also be required.

[sxa]

SPARC job doesn't seem to be doing too well: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-sparcv9-temurin-simple/

Compiling /export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/runtime/sweeper.cpp
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/abstractInterpreter.hpp", line 36: Error: Could not open include file "interp_masm_x86.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/templateTable.hpp", line 34: Error: Could not open include file "interp_masm_x86.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/templateTable.hpp", line 361: Error: Could not open include file "templateTable_x86_64.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/templateInterpreter.hpp", line 191: Error: Could not open include file "templateInterpreter_x86.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 122: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 128: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 130: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 134: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 134: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 134: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 134: Error: The type "InterpreterMacroAssembler" is incomplete.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 134: Error: Formal argument strings of type CodeStrings& in call to StubQueue::commit(int, CodeStrings&) is being passed int.
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/interpreter/interpreter.hpp", line 149: Error: Could not open include file "interpreter_x86.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/runtime/frame.inline.hpp", line 35: Error: Could not open include file "jniTypes_x86.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/runtime/frame.inline.hpp", line 101: Error: Could not open include file "frame_x86.inline.hpp".
"/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/src/share/vm/prims/methodHandles.hpp", line 184: Error: Could not open include file "methodHandles_x86.hpp".
16 Error(s) detected.
gmake[6]: *** [/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/make/solaris/makefiles/rules.make:143: sweeper.o] Error 2
gmake[5]: *** [/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/make/solaris/makefiles/top.make:112: the_vm] Error 2
gmake[4]: *** [/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/hotspot/make/solaris/Makefile:226: product] Error 2
gmake[3]: *** [Makefile:231: generic_build2] Error 2
gmake[2]: *** [Makefile:177: product] Error 2
gmake[1]: *** [HotspotWrapper.gmk:45: /export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/build/solaris-x86_64-normal-server-release/hotspot/_hotspot.timestamp] Error 2
gmake: *** [/export/home/local/vagrant/temurin-build/build-farm/workspace/build/src//make/Main.gmk:110: hotspot-only] Error 2
OpenJDK make failed, archiving make failed logs
Copying build.log to TemurinLogsArchive
Archiving and compressing with pigz
Your archive was created as /export/home/local/vagrant/temurin-build/build-farm/workspace/build/src/build/solaris-x86_64-normal-server-release/OpenJDK.tar.gz
Moving the artifact to location /export/home/local/vagrant/temurin-build/build-farm/workspace/target//jdk8u-hotspot.tar.gz

real	0m2.443s
user	0m0.014s
sys	0m0.020s

[sxa]

Both x64 and SPARC jobs are now running successfully. A top level pipeline has also been put in place to allow it to schedule the build, signing, test and release jobs.
The underlying build jobs take a RELEASE or WEEKLY value as booleans so that RELEASE=true causes the correct pipelines to execute.
The proxy agent is running as the solarisbuild user on dockerhost-azure-ubuntu2204-x64-1

• Example x64 pipeline for WEEKLY runs
• Example x64 pipeline for RELEASE
• Example sparcv9 pipeline for WEEKLY

[sxa]

Publish is currently happening with a filename containing the TIMESTAMP specified to the release job instead of the tag, but otherwise the pipelines are now working.