Add py-frites

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!97

Add py-viziphant

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!91

Add py-elephant

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!90

Add py-neo

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!86

Add py-quantities

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!85

Fix oppulance: Explicitly depend on modern flex version

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!95

Fix oppulance

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!94

If starting from scratch the archive file isn't there in do_fetch;
in this case, we can make use of the folder where the freshly
downloaded resources are cloned to.

Add oPPUlance (the SDK for the embedded processors (aka PPUs) on BrainScaleS)

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!73

Add py-neo, which is a dependency for py-elephant and py-pynn. An older version is available in upstream Spack.

Add py-quantities, which is a dependency for py-neo. This same version is available in upstream Spack, adding it here in case we need to add new versions quickly

Pin py-torch to 1.9.1

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!83

(due to a known build fail of 1.10.x → to be investigated later)

Cleanup and fix py-torch concretization

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!82

Dependency on py-pybind11 now "open" interval… (i.e. later than 2.6.2
allowed for newer version of pytorch).

Previously, we had compiler and python mentioned as specs and relied
on "together" concretization to pin the dependencies. Now, we provide
these constraints via "packages" section, providing global constraints.
Site-specific things, like "mpi" provider/external libs, or architecture
"target" constraints would also go in there…

new NMPI Client release

See merge request technical-coordination/project-internal/devops/platform/ebrains-spack-builds!78