Update noaacloud data paths to come from lustre mount linked to noaa-nws-global-pds bucket

[TaylorRoper-NOAA]

Description

This PR updates the noaacloud data paths to come from an FSx for Lustre mount provisioned with a data repository association to the S3 bucket noaa-nws-global-pds.

Resolves #4212

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
• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO (will update docs/source/noaa_csp.rst once cloud testing done)
• Does this change require an update to any of the following submodules? YES
  • EMC verif-global
  • GDAS NOAA-EMC/GDASApp#1993
  • GFS-utils
  • GSI NOAA-EMC/GSI#953
  • GSI-monitor
  • GSI-utils
  • UFS-utils
  • UFS-weather-model
  • wxflow

How has this been tested?

• Clone and update GSI and GDASApp hashes (see above linked PRs)
• Build GFS, GSI, and GDAS
• C96C48 cycled GFS atm-only test w/ 80 ens mems on AWS (reported improvements in Update noaacloud paths to utilize AWS FSx for Lustre DRA link to S3 bucket functionality #4212)

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