Set ci-runner concretizer and view configuration in higher scope

[CodeGat]

References ACCESS-NRI/build-ci#195

Background

It seems that build-ci spack manifests should almost always use concretizer.unify: when_possible as the concretization will fail when installing multiple of the same model component packages. Instead of having to create a schema on build-ci spack manifests, we should set this configuration higher up than the environment level (namely, here!).

This only solves half the problem, though. If a view can't be created due to having the same prefix (say, installing two mom5s with different compilers) the installation will fail. Hence we either need to have no view (which needs to be tested), or we need to set a custom spack.views.default.projections section in the spack manifest. Since it's not a first order configuration file (like config.yaml or concretizer.yaml, we need to inject this file into the environment. This is why it's called injected.view.yaml.

The PR

• Update ci-runner concretizer to contain unify: when_possible
• Create injected.view.yaml snippet for ci-runner spack manifests

[CodeGat]

Going to test out using the above spack configuration with the compose file.