Add back 1.25 deg WAFS blending when separating WAFS updates from GFSv16.3.11

[YaliMao-NOAA]

#2100

PR #2100 separates WAFS updates from GFSv16.3.11

Description

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)? YES/NO
• Does this change require a documentation update? YES/NO

How has this been 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
• My changes generate no new warnings
• New and existing tests pass with my changes
• I have made corresponding changes to the documentation if necessary

[KateFriedman-NOAA]

Thanks for catching this @YaliMao-NOAA !

[KateFriedman-NOAA]

@YaliMao-NOAA For further confirmation, I see the wafs_blending job running in ops still with the new gfs_ver=v16.3.11:

kate.friedman@dlogin04:/lfs/h1/ops/prod/output/20231204> date
Mon Dec  4 17:03:24 UTC 2023
kate.friedman@dlogin04:/lfs/h1/ops/prod/output/20231204> ls -ltr *wafs*blending* | grep -v 0p25
-rw-r--r-- 1 ops.prod prod 421095 Dec  4 04:33 gfs_atmos_wafs_blending_00.o118884423
-rw-r--r-- 1 ops.prod prod 421239 Dec  4 10:33 gfs_atmos_wafs_blending_06.o119049182
-rw-r--r-- 1 ops.prod prod 420626 Dec  4 16:33 gfs_atmos_wafs_blending_12.o119214550
kate.friedman@dlogin04:/lfs/h1/ops/prod/output/20231204> grep gfs_ver= gfs_atmos_wafs_blending_12.o119214550
+++ 0 + export gfs_ver=v16.3.11
+++ 0 + gfs_ver=v16.3.11
++ 0 + eval 'export gfs_ver=v16.3.11'
+++ 0 + export gfs_ver=v16.3.11
+++ 0 + gfs_ver=v16.3.11
0 + export gfs_ver=v16.3.11
0 + gfs_ver=v16.3.11
gfs_ver=v16.3.11