Infra Update v8: spack v1 Support

[CodeGat]

References issue ACCESS-NRI/build-cd#313 and PR ACCESS-NRI/build-cd#326
References rollout issue ACCESS-NRI/build-cd#328
References project Spack `0.22` to `1.0` Migration

Important

This PR is a major update to the deployment infrastructure. See below for the prerequisites for this repository to be able to merge this PR.

Important

This major version change marks the end of major infrastructure updates for deployments to spack < 1.0.
If you want to deploy to instances of spack < 1.0, you must use build-cd < v8.
If you want to deploy to instances of spack >= 1.0, you must use build-cd >= v8.

Background

We are moving on up to spack v1! This update to spack contains many bug fixes, optimisations and new features that can be incorporated into build-cd.

This update also contains changes that make spack v0.X incompatible with this build-cd v8 update - the most prominent one being the splitting of spacks core codebase from it's builtin spack-packages repo. This means that for provenance, one to keep track of both builtin spack-packages and our own, renamed access-spack-packages. build-cd will centrally control the version of builtin spack-packages for a given instance, and config/versions.jsons spack-packages key is renamed to access-spack-packages.

As noted earlier, this major version of build-cd can only support spack v1, due to spack v1-specific commands in the infrastructure. If you still want to deploy to spack v0.X, you will need to change build-cd to v7, and update the config/versions.json file/spack.yaml.

Features

• Support for spack v1: We're moving to a new, non-beta version of spack! It contains bug fixes, features and optimisations over the old version.

Prerequisites for Merging

• Update build-cd entrypoints (this PR!)
• Update config/versions.json with new inputs (also this PR!)
• Validate compiler additions to the spack manifest (this PR, too!)
• Test and Verify Model built with spack v1

---

🚀 The latest prerelease access-ram3/pr24-3 at 4d7b408 is here: #24 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-ram3 Prerelease pr24-1 with commit 26c053c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-ram3 Prerelease pr24-2 with commit b0e595b

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-ram3 Prerelease pr24-3 with commit 2084725

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-ram3 Prerelease pr24-3 with commit 4d7b408

🖥️ Gadi Deployment ❌

[CodeGat]

Just noting that the deployment succeeded, but there was an issue gathering metadata that was unrelated to the spack side of things. That should be good to test!

[CodeGat]

The issue is that we don't have an appropriate ref to upload for the release database for the um package. Usually we use um_ref variant but that isn't in this model. Hmmm...