Setup CI/CD

[CodeGat]

We have a good base for CI/CD with https://github.com/ACCESS-NRI/ACCESS-OM2/tree/main/.github/workflows. But this was done without knowing what pieces of the CI/CD are sufficiently generic for each new model. Using a new model will be a good test for how generic we can make certain aspects of the pipeline, which we can then add to https://github.com/ACCESS-NRI/build-cd

Some todos:

• Add JSON Validation for config
• Add some way to version this model from within the spack.yaml #3
• Determine Suitability of Prerelease Pipeline
• Determine Suitability of Release Pipeline (as well as tagging)
• Generally - determine what we can do to make creation of CI/CD pipelines for other spack-based models easier

[CodeGat]

If all of the models follow the same spack.yaml structure, this could be simplified massively. See drafted ACCESS-NRI/build-cd#47