Add WCOSS2 site config

[AlexanderRichert-NOAA]

Summary

Add WCOSS2 configuration prior to 1.9.0 release.

Testing

Tested concretize, install, and module build on Acorn (note the use of core_compilers, i.e., no more metamodules).

Applications affected

NCO stack

Systems affected

Acorn/WCOSS2

Dependencies

none

Issue(s) addressed

NOAA-EMC/WCOSS2-requests#13

Checklist

• This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
• These changes have been tested on the affected systems and applications.
• All dependency PRs/issues have been resolved and this PR can be merged.

[AlexanderRichert-NOAA]

@WeiWei-NCO please take a look if you get a chance. This should encapsulate everything I've already incorporated into release/1.6.0-nco, idea being that in the future, starting with 1.9.0, we shouldn't need a separate NCO branch.

[WeiWei-NCO]

Nothing jumps out at me.

starting with 1.9.0, we shouldn't need a separate NCO branch.

As long as each code delivery from EMC has a new version number, and only the related files get updated. We don't expect many spack-stack changes or package.yaml changes in the spack sub when the delivery is only to upgrade certain library/libraries.

[climbfuji]

@AlexanderRichert-NOAA I changed the base branch to release/1.9.0 (let's merge site config updates directory into the release branch, then bring everything back to develop once the release is tagged). Can you please merge this when you think it is ready (maybe ping @Hang-Lei-NOAA to review and approve)?

[AlexanderRichert-NOAA]

Sounds good, will do, thanks.

I need to revert one module-related change then this is ready to go.