Update global_workflow_env with the most recent required libraries

[DavidHuber-NOAA]

Is your feature request related to a problem?

The global workflow environment is out of date and needs to be updated to include the required libraries for current development work.

Describe the solution you'd like

The libraries required should be updated in https://github.com/JCSDA/spack-stack/blob/develop/repos/spack_stack/spack_repo/spack_stack/packages/global_workflow_env/package.py to reflect the current libraries used by the package. Alternatively (perhaps better), the environment should be updated to be modular and inherit its needs from the associated submodules (UFS-WM, GSI, GDASApp, UPP, verif-global, UFS_Utils). These packages' environments should also be updated.

Additional context

Originally discussed in #1993

[DavidHuber-NOAA]

@climbfuji @AlexanderRichert-NOAA what are your thoughts on a modular approach? Should the global-workflow-env only include the modules required for the global workflow, but not its submodules, or should it include everything needed by all submodules and the global workflow? Just noting, if it's the latter, then the global-workflow-env will be very close to the unified-env.

[climbfuji]

I believe the global-workflow-env should contain everything that is needed to run the global workflow. The unified environment will still be larger, because it contains the different jedi-HOSTMODEL environments, too.

[DavidHuber-NOAA]

That makes sense to me. Thanks @climbfuji. I'll get the environment updated.

[benjamin-cash]

I really like the idea of a modular approach. You could also extend the modular aspect to the basic component of the weather model. For example, building MAPL is a non-trivial exercise. The Seasonal Forecast System configuration of the model does not include aerosols - if that is the application I want to run it seems like there should be a straightforward way for me to build a library stack without it.