add yamls to be used for retro

[JessicaMeixner-NOAA]

Description

Yamls to be used for GFSv17 retros.

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 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? NO (If YES, please add a link to any PRs that are pending.)
  • EMC verif-global
  • GDAS
  • GFS-utils
  • GSI
  • GSI-monitor
  • GSI-utils
  • UFS-utils
  • UFS-weather-model
  • wxflow

How has this been tested?

Just minor updates to existing yamls which have been extensively tested.

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

[RuiyuSun]

Should the SDATE_GFS be aligned with the idate: 2025111306 in dev/ci/cases/gfsv17/retrov17_realtime.yaml. SDATE_GFS: 2025111312?

[JessicaMeixner-NOAA]

@DavidHuber-NOAA - what is needed for this PR to move forward?

[DavidHuber-NOAA]

Looks good.

[DavidHuber-NOAA]

Merging based on @CatherineThomas-NOAA's review as there are no CI-testable changes.