Custom model names with !update-configs

[anton-seaice]

Related to #329

The !update-configs keyword action doesn't support custom projections/module names

e.g. if a spack environment uses custom module names, !update-configs needs to be aware of these and choose the right one

Example custom module name

  modules:
    default:
      tcl:
        projections:
          access-om2: '{name}/2026.02.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'

running !update-configs, tries to use

modules:
  load:
  - access-om2/pr133-6

but it should try to use the custom module name

e.g.

modules:
  load:
  - access-om2/pr133-6/2026.02.000-360x300

[CodeGat]

Thanks for picking up this bug - I'll look into it

[anton-seaice]

I think it's low priority