Rename EE2 Environment Variables: Replace NET-Specific (VARgfs) with Global (VARglobal) Naming

[AntonMFernando-NOAA]

Description

• This pull request standardizes environment variable naming across the global-workflow repository for EE2 compliance. All variables and paths previously using NET-specific names (e.g., HOMEgfs_, VARgfs, HOME$NET$ etc.) have been renamed to use the new global convention (e.g., HOMEglobal_, VARglobal). This improves clarity, maintainability, and prepares the codebase for multi-NET extensibility.
  Resolves Rename EE2 variables with NET from VARgfs to VARglobal (or similar) #4410

Key updates

• Added dev/ush/convert_net_to_global.sh to convert all NET-specific variable and path names to the new global naming convention.
• Added dev/ush/convert_global_to_net.sh to revert global variable and path names back to NET-specific naming if needed.
• These scripts ensure consistency and reduce manual effort when transitioning the codebase or maintaining compatibility with older workflows.

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 #216
  • GDAS #2073
  • GFS-utils
  • GSI
  • GSI-monitor #202
  • GSI-utils
  • UFS-utils #1132
  • UFS-weather-model
  • wxflow

How has this been tested?

• Regular CI tests on HERA and extended cases on wcoss2

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