Roll out spack-stack-1.6.0

[climbfuji]

Is your feature request related to a problem? Please describe.

This issue captures the necessary tasks for rolling out spack-stack-1.6.0.

Installation procedure:

1. Install unified-env from release/1.6.0 branch of spack-stack (and spack submodule)
2. Install gsi-addon-env on selected platforms as chained environment (see list of platforms below)
3. Update documentation and site config for each site (as necessary), including information about gsi-addon-env

Describe the solution you'd like

1. Installation completed following the above procedure:
   • Hercules (Intel, GNU) - needs gsi-addon-env (@climbfuji)
     • Extra step: add fms@2023.02.01, sp@2.3.3, and crtm@2.4.0 to unified-env because of Spack-stack 1.5.1, ESMF 8.5.0, FMS 2023.02.01 + Remove Gaea C4 + Fix build system to allow CMAKE_<COMPILER>_FLAGS to be specified for submodules #2052 ufs-community/ufs-weather-model#2013 (@climbfuji)
   • Orion (Intel, GNU) - needs gsi-addon-env (@climbfuji)
   • Nautilus (Intel) (@climbfuji)
   • Narwhal (Intel) (@climbfuji)
   • Narwhal (GNU) (@climbfuji)
   • S4 (Intel) - needs gsi-addon-env (@climbfuji)
   • Discover (Intel, GNU) (@climbfuji)
   • Hera (Intel, GNU) - needs gsi-addon-env: (@RatkoVasic-NOAA)
   • Jet (Intel, GNU) - needs gsi-addon-env: (@RatkoVasic-NOAA)
   • Gaea C5 (Intel) (@RatkoVasic-NOAA)
   • Acorn (Intel, GNU) (@AlexanderRichert-NOAA)
   • Casper (GNU) (@climbfuji)
   • Derecho (Intel, GNU) (@climbfuji)
   • AWS Single Node AMI Red Hat 8 (GNU) in progress (@climbfuji)
     • spack-stack-1.6.0 build
     • testing, clean up and creation of new AMI
     • AMI skylab-7.0.0-redhat8 in JCSDA USAF account, us-east-2 is ami-091ad0584d0400762
     • AMI skylab-7.0.0-redhat8 in JCSDA USAF account, us-east-1 is ami-01147e0e00b99cbdf
   • JCSDA AWS Parallel Cluster (R&D) (Intel, GNU) (@climbfuji)
   • NOAA Parallelworks Gcloud JCSDA (Intel) (@climbfuji)
   • NOAA Parallelworks Gcloud EPIC (Intel) in progress (@natalie-perlin)
   • JCSDA CI containers (@climbfuji)
2. Prepare release tags
   • Tag spack submodule as spack-stack-1.6.0
   • Update release/1.6.0 to tag spack-stack-1.6.0 of spack submodule in container recipes and .gitmodules
   • Update documentation (container doc, readthedocs): version, etc.
   • Tag spack-stack as 1.6.0 and spack-stack-1.6.0
   • Switch readthedocs from release/1.6.0 to 1.6.0
   • Create and publish release notes
3. Remove spack-stack-v1 (containing skylab-3.0.0 releases and older) from all supported platforms. Check if any of the legacy thirdparty packages can be removed. Configure remotes and check out final tags 1.6.0/spack-stack-1.6.0 in spack-stack-1.6.0 directory.
   • Hercules
   • Orion
   • Nautilus
   • Narwhal
   • S4
   • Discover
   • Hera
   • Jet
   • Gaea
   • Acorn
   • Casper
   • Derecho
   • AWS Single Node AMI Red Hat 8 (GNU)
   • JCSDA AWS Parallel Cluster (R&D)
   • NOAA Parallelworks Gcloud JCSDA
   • JCSDA CI containers n/a
4. Merge release branches back into jcsda_emc_spack_stack / develop:
   • spack: Merge release/1.6.0 into jcsda_emc_spack_stack spack#392
   • spack-stack Merge release/1.6.0 into develop #949

Additional context
n/a

[junwang-noaa]

@climbfuji can you write a list of updated libraries in release/1.6.0? I think the library team (@Hang-Lei-NOAA @AlexanderRichert-NOAA ) need to test them on acorn and once confirmed, make requests for installation on wcoss2, which could take some time to finish. We are trying to avoid the libraries to diverge on wcoss2.

[climbfuji]

Can EPIC or EMC do this please? @AlexanderRichert-NOAA @ulmononian