Add an e3sm_omega_developer CIME test suite

[andrewdnolan]

This PR adds a e3sm_omega_developer test suite, comprised of SMS and ERS test for Omega. As part adding this test suite, some modifications to the existing compsets were addded:

• Updated to newest JRA data source (JRA1p5).
• Added an Omega testmod, to limit data download to 1958.
• Add a missing entry in Omega's archive configuration.

Checklist

• Documentation:

  • Design document has been generated and added to the docs
  • User's Guide has been updated
  • Developer's Guide has been updated
  • Documentation has been built locally and changes look as expected

• Linting

  • Pre-commit run locally

• Building

  • CMake build does not produce any new warnings from changes in this PR

• Testing

  aurora, oneapi-ifx, mpich

  • CTests Pass
  • Polaris omega_pr Pass

  chrysalis, oneapi-ifx, openmpi

  • CTests Pass
  • Polaris omega_pr Pass

  frontier, craygnu, mpich

  • CTests Pass
  • Polaris omega_pr Pass

  frontier, craygnu-mphipcc, mpich

  • CTests Pass
  • Polaris omega_pr Pass

  pm-cpu, gnu, mpich

  • CTests Pass
  • Polaris omega_pr Pass

  pm-gpu, gnugpu, mpich

  • CTests Pass
  • Polaris omega_pr Pass

• Provide relevant details in a comment to the PR titled Testing with the following:

  • Which machines CTest unit tests
    have been run on and indicate that are all passing.
  • The Polaris omega_pr test suite
    has passed, using the Polaris e3sm_submodules/Omega baseline
  • Document machine(s), compiler(s), and the build path(s) used for -p for both the baseline (Polaris e3sm_submodules/Omega) and the PR build
  • Indicate "All tests passed" or document failing tests
  • Document testing used to verify the changes including any tests that are added/modified/impacted.

• Performance related PRs: Please include a relevant PACE experiment link documenting performance before and after.

• New tests:

  • CTest unit tests for new features have been added per the approved design.
  • Polaris tests for new features have been added per the approved design (and included in a test suite)

• Stealth Features

  • If any stealth features are included in the PR, please confirm that they have been documented.

[andrewdnolan]

PEM tests have been commented out in the test suite definition, because they fail with a CIME error when run as part of a testsuite.

The same PEM test run as a standalone test will pass, but CIME errors out during the run phase when run as part of a suite.

Here are some example paths, on chrysalis, to investigate for those interested:

/lcrc/group/e3sm/ac.anolan/scratch/chrys/PEM_Vmct.T62_oQU240.COMEGA-IAF.chrysalis_gnu.20260807_200345_aihpv7 # <--- (FAIL) part of a suite 
/lcrc/group/e3sm/ac.anolan/scratch/chrys/PEM_Vmct.T62_oQU240.COMEGA-IAF.chrysalis_gnu.20260807_201631_14aim4 # <--- (PASS) standalone test

[andrewdnolan]

Testing:

On Frontier:

./create_test --compiler craygnu e3sm_omega_developer

Results (All-PASS):

  ERS_Vmct_Ln5.TL319_EC30to60E2r2.COMEGA-JRA1p5.frontier_craygnu.omega-jra_1958 (Overall: PASS)
  ERS_Vmct.T62_oQU240.COMEGA-IAF.frontier_craygnu (Overall: PASS)
  SMS_Vmct_Ln5.TL319_EC30to60E2r2.COMEGA-JRA1p5.frontier_craygnu.omega-jra_1958 (Overall: PASS)
  SMS_Vmct.T62_oQU240.COMEGA-IAF.frontier_craygnu (Overall: PASS)