master Scheduled Build-CI Fix

[CodeGat]

Background

In order to get the {{ scheduled_ref }} for the manifests, we need to git rev-parse the HEAD of the branch. We had updated the checkout logic to checkout access-esm1.5 instead of master so we could get that HEAD in the access-esm1.5 case, but the manifests themselves weren't in that branch! So we should move the manifests that deal with scheduled checks out of the master branch, into the branch that they'll be used.

So now, instead of the old directory structure, which namespaced scheduled tests by branch name on master, we don't have to separate them, as they are on their own branch. Instead, we have:

On master:
.github/
├── build-ci/
│   ├── data/
│   │   └── standard.json
│   └── manifests/
│       ├── pr/
│       │   └── ...
│       └── scheduled/
│           ├──  gcc_mom_access-esm1.6.spack.yaml.j2
│           └── ...
└── workflows/
    ├── ci.yml
    └── scheduled.yml

On access-esm1.5:
.github/
├── build-ci/
│   ├── data/
│   │   └── standard.json
│   └── manifests/
│       ├── pr/
│       │   └── ...
│       └── scheduled/
│           ├── gcc_mom_access-esm1.5.spack.yaml.j2
│           ├── intel_mom_access-esm1.5.spack.yaml.j2
│           └── oneapi_mom_access-esm1.5.spack.yaml.j2
└── workflows/
    └── ci.yml

So this PR removes the namespacing of scheduled tests, and deletes the access-esm1.5-specific ones (to be moved to the access-esm1.5 branch).

The PR

• Move scheduled/master manifests under scheduled
• Delete scheduled/access-esm1.5 (move to access-esm1.5 branch)
• Remove branch namespacing, rev-parse HEAD instead of origin/BRANCH

[dougiesquire]

Thanks @CodeGat. oasis3_mct_version_esm1p5 can now be removed from ./build-ci/data/standard.json, but otherwise LGTM

[dougiesquire]

It looks like the current exclusion is actually in the wrong place. We want:

• master: exclude .github/build-ci/manifests/scheduled/gcc_mom_access-esm1.6.spack.yaml.j2
• access-esm1.5: exclude .github/build-ci/manifests/scheduled/gcc_mom_access-esm1.5.spack.yaml.j2

[dougiesquire]

It also looks like the version of oasis3-mct that we use in access-esm1.5 doesn't build with oneapi. Let's exclude:

• access-esm1.5: exclude .github/build-ci/manifests/scheduled/oneapi_mom_access-esm1.5.spack.yaml.j2

[dougiesquire]

Approving now because I'm so confident we're there.

Test of the scheduled workflow is running here: https://github.com/ACCESS-NRI/MOM5/actions/runs/16870417116