Enable awscli-v2 in ewok-env/jedi-tools-env, update gmao-swell-env (includes PR https://github.com/JCSDA/spack/pull/332)

[climbfuji]

Description

• Bug fix in py-awscrt, adding missing dependencies on cmake (all platforms) and openssl (Linux)
• Replace awscli with awscli-v2 in ewok-env and jedi-tools-env
• Bug fixes in gmao-swell-env: simplify dependency trees

This PR includes #332 (cherry-picked), i.e. when it gets closed it will automatically close #332 as completed, too.

Testing

See JCSDA/spack-stack#813

Note that the "CI failure" below is a codecov error with minimal changes that we should ignore.

Issues

See JCSDA/spack-stack#813

[ashley314]

I don't see any issues, but I am also not familiar with the requirements for the gmao-swell-env. I tested previously for awscli-v2 on my mac with no issues.

[srherbener]

Just for my learning: the BundlePackage is a spack mechanism for specifying a set of dependencies, requirements, variant's, conflicts, etc. (but no actual build) that are needed for another package/system defined/installed somewhere else. So in this case SWELL is a development system that is not managed by spack, but requires a certain set of packages/versions/etc that are being managed by spack. Am I understanding this correctly? Thanks!

[climbfuji]

Just for my learning: the BundlePackage is a spack mechanism for specifying a set of dependencies, requirements, variant's, conflicts, etc. (but no actual build) that are needed for another package/system defined/installed somewhere else. So in this case SWELL is a development system that is not managed by spack, but requires a certain set of packages/versions/etc that are being managed by spack. Am I understanding this correctly? Thanks!

These virtual envs are convenient for us to define dependencies and to create modules that load whatever is needed for a specific application.