Incorporate upstream MOM6 updates

[aidanheerdegen]

Another copy of #23 but with a squashed commit history to see if that makes a difference.

---

🚀 The latest prerelease access-om3/pr26-1 is here: #26 (comment) 🚀

[github-actions]

🚀 Deploying access-om3 2024.09.1 as prerelease pr26-1 with commit 354d40a

Details and usage instructions

This access-om3 model will be deployed as:

• 2024.09.1 as a Release (when merged).
• pr26-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr26-1

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2024.07.08
• access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

[CodeGat]

Hey, due to ACCESS-NRI/build-cd#173 we have had to update the infrastructure in this repository, as well - see #28.

We try and keep these kinds of updates to a minimum, and, starting from this one onwards, it will no longer be a hard requirement to update PR branches to incorporate infrastructure changes in order for the infrastructure to work - as you need to for this one.

To update this PR to the new origin/main, do the following:

git pull
git rebase origin/main
git push --force

to incorporate CI changes into the PR.

Your PR may redeploy, but that is okay - it should be identical to the last deployment. Let me know if you have any questions or issues.

[chrisb13]

Closing as it's easier to start again given the infrastructure and change of approach changes.