Update g-w gfsv17 Branch to the Latest UFS_UTILS Submodule Update in gfsv17 Branch

[AntonMFernando-NOAA]

Description

• This PR updates the gfsv17 branch to the latest UFS_UTILS submodule (GFS.v17.0.0)

  Refs #1133

Type of change

• Bug fix (fixes something broken)
• New feature (adds functionality)
• Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

• Is this change expected to change outputs (e.g. value changes to existing outputs, new files stored in COM, files removed from COM, filename changes, additions/subtractions to archives)? YES/NO (If YES, please indicate to which system(s))
  • GFS
  • GEFS
  • SFS
  • GCAFS
• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO
• Does this change require an update to any of the following submodules? YES
  • EMC verif-global
  • GDAS
  • GFS-utils
  • GSI
  • GSI-monitor
  • GSI-utils
  • UFS-utils #1133
  • UFS-weather-model
  • wxflow

How has this been tested?

• All available CI tests were run on WCOSS2 and passed successfully.
• CI tests ran with gfsv17 branch (with the updated ufs_utils submodule) can be found here: /lfs/h2/emc/stmp/anton.fernando/RUNTESTS/EXPDIR
/C96C48mx500_S2SW_cyc_gfs_t1
/C96_atm3DVar_extended_t1
/C48_S2SW_extended_t1
/C96C48_hybatmsnowDA_t1
/C96C48_hybatmsoilDA_t1
/C96mx100_S2S_t1
/C48mx500_3DVarAOWCDA_t1
/C48_ATM_t1
/C48mx500_hybAOWCDA_t1
/C96C48_hybatmDA_t1

Checklist

• Any dependent changes have been merged and published
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have documented my code, including function, input, and output descriptions
• My changes generate no new warnings
• New and existing tests pass with my changes
• This change is covered by an existing CI test or a new one has been added
• Any new scripts have been added to the .github/CODEOWNERS file with owners
• I have made corresponding changes to the system documentation if necessary

[JessicaMeixner-NOAA]

Thank you @AntonMFernando-NOAA for making this PR!

@DavidHuber-NOAA - can we use the automated CI to run the gaea tests or do I need to run those on my end?

[DavidHuber-NOAA]

@JessicaMeixner-NOAA unfortunately, the automated CI will not work for the dev/gfs.v17 branch for technical reasons, so it needs to be manually tested.

[ClaraDraper-NOAA]

Looks good to me - this will bring the UFS_UTILS up to the intended version.

Is the ccpp-physics version in (this) v17 branch consistent with the version in the ufs-model v17 branch?

[AntonMFernando-NOAA]

Looks good to me - this will bring the UFS_UTILS up to the intended version.

Is the ccpp-physics version in (this) v17 branch consistent with the version in the ufs-model v17 branch?

@ClaraDraper-NOAA: @BrianCurtis-NOAA added the latest CCPP-Physics version to the gfsv17 UFS_UTILS branch when it was being created. I’m not knowledgeable enough to know whether ufs-model is consistent with that version.

[BrianCurtis-NOAA]

Looks good to me - this will bring the UFS_UTILS up to the intended version.
Is the ccpp-physics version in (this) v17 branch consistent with the version in the ufs-model v17 branch?

@ClaraDraper-NOAA: @BrianCurtis-NOAA added the latest CCPP-Physics version to the gfsv17 UFS_UTILS branch when it was being created. I’m not knowledgeable enough to know whether ufs-model is consistent with that version.

UFSWM production/gfsv17 points to:

[submodule "UFSATM"]
  path = UFSATM
  url = https://github.com/NOAA-EMC/ufsatm
  branch = production/GFS.v17

which has a ccpp-physics hash: https://github.com/ufs-community/ccpp-physics/tree/d29ad83bc455b76d9a9b907d5f7be1c717a9646e