Update externals to match beta05

[peverwhee]

Tag name (required for release branches): tentative sima0_03_001
Originator(s): peverwhee

Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):

• Updates externals to match CESM beta05 tag
• Add CUPiD external
• Adds additional git-fleximod workflow test
• Small fix to test_driver.sh to agree with new externals

closes #361

Describe any changes made to build system: n/a

Describe any changes made to the namelist: n/a

List any changes to the defaults for the input datasets (e.g. boundary datasets): n/a

List all files eliminated and why: n/a

List all files added and what they do:
A tools/CUPiD

• add new CUPiD submodule

List all existing files that have been modified, and describe the changes:
(Helpful git command: git diff --name-status development...<your_branch_name>)

M .github/workflows/fleximod-test.yaml

• add new test to confirm what is checked out with git-fleximod matches the expected submodules

M .gitmodules

• update externals to match beta05

M ccs_config
M cime
M components/cdeps
M components/cism
M components/clm
M components/cmeps
M components/mizuRoute
M components/mosart
M components/rtm
M libraries/FMS
M libraries/parallelio
M share

• submodule updates

M test/system/test_driver.sh

• Remove --queue argument from testargs for derecho (to match CAM usage)

If there are new failures (compared to the test/existing-test-failures.txt file),
have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?

derecho/intel/aux_sima: All NLFAIL due to NUOPC external update

derecho/gnu/aux_sima: All NLFAIL due to NUOPC external update

If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced: n/a

CAM-SIMA date used for the baseline comparison tests if different than latest:

[nusbaume]

Thanks for seeing this update through @peverwhee!