metdata.yaml names inconsistent

[anton-seaice]

We appear to use the model name field a bit inconsistently:

e.g. in

model: ACCESS-OM2 is in some of the 025deg configs

access-om2-configs/metadata.yaml

Line 33 in da5f796

model: ACCESS-OM2

model: access-om2-01

in

access-om2-configs/metadata.yaml

Line 28 in 83885a4

model: access-om2-01

We need to confirm whether the case matters, and whether we want to put a CI check in for this.

The desired names seem to be

ACCESS-OM2
ACCESS-OM2-025
ACCESS-OM2-01