…gs in not only pybind11 but also moo, and only have an explicit (run-time) dependence on moo if python configuration is used in a package

…nly if they're only used in unit tests)

…hat's actually available on the web

…n we're dealing with a developer installation

…kage, which lets you choose whether you want to include developer tools (daq-cmake, cmake, etc.)

…s needed when generating configs, come up with a ~dev version of daq-cmake which can still provide this while not bringing in its dependencies

…installation of dunedaq will work

Conflicts:
	spack-repos/release-repo-template/packages/cmdlib/package.py
	spack-repos/release-repo-template/packages/dfmessages/package.py
	spack-repos/release-repo-template/packages/dfmodules/package.py
	spack-repos/release-repo-template/packages/dqm/package.py
	spack-repos/release-repo-template/packages/serialization/package.py
	spack-repos/release-repo-template/packages/sspmodules/package.py
	spack-repos/release-repo-template/packages/timing/package.py
	spack-repos/release-repo-template/packages/trigger/package.py

…the possibly-unavailable sh module

…variant of daq-cmake

… machines at CERN, but is now part of the standard docker installation

…eflect updated dependencies

Conflicts:
	spack-repos/release-repo-template/packages/appfwk/package.py

… dependencies

…nctions (daq_add_python_bindings, etc.) only depend on daq-cmake in the build phase

…_model_path function where necessary

… daq-cmake is built, but IS needed by other packages which use it

…pybind11 and py-moo

… under the ~dev option

…the Python virtual environment and thus doesn't need to be specified as a Spack run-time dependency

…nt of externals continue to not depend on devtools, but regardless still depend on the systems umbrella package (needed for openssh and parts of gcc)