Force Spack to add library paths to LD_LIBRARY_PATH when installing a library.

Updating Spack in our workflow introduced a bug in our workflow. Spack is by default not updating the LD_LIBRARY_PATH anymore to ensure that installations from Spack do not affect the underlying system. Instead, it uses RPATH and writes the library path directly into the executable.

Since we are using Spack here to create an environment to build our frameworks in, we required the paths to be publically known.

---

Fix: Override the default to append the LD_LIBRARY_PATH variable using prefix_inspections on a modules level (for every installed module) for every package that is being installed in the environment. Furthermore, disable view to force Spack to use the paths where the packages are actually installed.