WOMBAT-lite testing for ACCESS OM2 and OM3

[chrisb13]

As discussed with @pearseb, @aidanheerdegen, @anton-seaice, @CodeGat ..

Long-term goal is to have both reproducibility testing and build checks occurring for wombat-lite for ACCESS OM2 and OM3. Starting point (probably easier) is to have build checks. What do we need to get started @CodeGat?

Starting point question for @pearseb: which fields would capture reproducibility / non-repro in Wombat?

[anton-seaice]

For build checks, once the "development" branch is merged, so that the CMakeLists is included, then all that's needed is to add a copy of this ci definition to this repository:

https://github.com/ACCESS-NRI/cice5/blob/master/.github/workflows/model-build-test-ci.yml

This will trigger a spack build of this the generic tracers library for every pull request and push.

For repro tests, these could look like:

• add some BGC specific global fields to the ocean.stats output of MOM. These would be global totals.
• check if these are captured automatically in "model-config-tests"
• update the OM2 and OM3 configs which include BGC to include the added fields in the checksums file