[dev/gfs.v17] Update the production/GFS.v17 UFS WM hash

[dpsarmie]

Description

This PR will update the UFS Weather Model hash to the latest GFS.v17 production hash 52f9b46. This hash includes updates to CCPP which include the following fixes (develop related PRs linked):

• Removal of select goto statements (Reduce goto in ufs-weather-model: ccpp/physics ufs-community/ufs-weather-model#3167)
• Updating the rte-rrmtgp submodule to production/GFS.v17 and adding a fix for a compiler warning (New RRTMGP compilation warning with v1.8 ufs-community/ccpp-physics#322)

These fixes were added into production and tested against the production v17 baselines using the UFSWM regression test workflow. These changes did not cause changes to the baselines.

Since this update will change the CCPP hash, an update to UFS-Utils will be needed before this PR can be merged.

The UFS-Utils update will need to occur after #4659 is merged since the UFS-Utils changes associated with that PR are already merged into the UFSU production branch.

Type of change

• 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)? NO
• 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
  • UFS-utils
  • UFS-weather-model [production/GFS.v17] Update UFSATM hash :: Remove some CCPP goto statements and fix rte-rrtmgp warning ufs-community/ufs-weather-model#3185

How has this been tested?

This was tested against the UFSWM baselines that were created for the GFSv17 production branch on Ursa and WCOSS2. This will still need to be tested with GW CIs once the CCPP hash in UFS Utils can be updated.

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