Add fftw and netlib-lapack as passive dependencies for jedi-neptune-env

[climbfuji]

Description

This PR adds fftw and netlib-lapack to jedi-neptune-env. jedi-neptune-env itself doesn't depend on it for building, but they need to be there for other reasons. I found a nice workaround, namely make them build-time dependencies instead of run-time dependencies. This way, the packages get installed and the modules are created, but loading jedi-neptune-env will not load fftw and netlib-lapack automatically.

I tested this on my macOS based on the latest develop code, and also on Nautilus for spack-stack-1.6.0.

Issue(s) addressed

Working towards JCSDA/spack-stack#941

Dependencies

n/a

Impact

n/a

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have run the unit tests before creating the PR

[AlexanderRichert-NOAA]

This is fine with me. Based on the description, would it make sense to have a "miscellaneous" metapackage for things like this or madis that don't really have any other home?

[climbfuji]

This is fine with me. Based on the description, would it make sense to have a "miscellaneous" meta-package for things like this or madis that don't really have any other home?

That's something we could explore, maybe with a slightly different name that indicates that we are going to suppress the module creation for that meta-package?