GHActions: Solaris10 is failing

Ref: #2420 #2424

As of my PR, #2405 , the GitHub action is failing, as it uses the same [Vagrantfile as VPC](https://github.com/adoptium/infrastructure/blob/master/ansible/vagrant/Vagrantfile.Solaris10) . However, as GitHub actions don't run on a set machine, we can't install the local box that I have on the VPC machine.

The box has the SolarisStudio compiler installed on it, so we can't have it accessible by the public (I think), which rules out storing it somewhere like `ci.adoptopenjdk.net/userContent/`, and also rules out putting it on the [Vagrant Box repository](https://app.vagrantup.com/boxes/search).

I'm unaware if GitHub Actions can run from a specific machine that we could pre-provision, or if they can have access to a private server to get the box from?

Start by reading the Solaris10 workflow context in PR #2405 and the referenced issues #2420 and #2424, then inspect ansible/vagrant/Vagrantfile.Solaris10. Determine whether GitHub Actions can use a pre-provisioned machine or access a private box containing SolarisStudio. Done means the Solaris10 GitHub Action has a supported, non-public way to obtain its required environment and runs successfully.

Written by the indexing model from the issue text.