Refactor job scripts to streamline configuration sourcing

[bbakernoaa]

Description

This pull request refactors the initialization of several job scripts to standardize how configuration files are sourced. The main change is to remove the use of the -c argument in the jjob_header.sh script and instead explicitly source each required config file within the job script itself. This makes the configuration sourcing more transparent and easier to manage.

Standardization of configuration sourcing in job scripts:

• Removed the -c argument from the source "${HOMEgfs}/ush/jjob_header.sh" command in all affected job scripts, simplifying the call and decoupling config sourcing from the header script. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]
• Explicitly sourced the relevant config files for each job script, such as config.base and other job-specific configs (e.g., config.gempak, config.wave_stat, etc.), immediately after sourcing the header script. This improves clarity and maintainability by making all required configuration files visible at the top of each script. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

Impacts #4550

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)? 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? 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?

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