ci: add spack ci

There is an ongoing effort from the DAV-SDK to utilize the UO Frank Cluster. The UO Frank Cluster provides a wide variety of relevant HW that we can test against https://systems.nic.uoregon.edu/internal-wiki/index.php?title=Category:Servers.

In addition to utilizing the UO Frank CI, we will eventually use the same integration systems to provide CI in Facilities such as Frontier in the future, which is one of the DAV SDK main objectives.

This first step is a proof of concept that adds an mpich linux x86 build in the spack CI and it will run for every commit in master. In the future we will provide future platforms/arch and will will provide CI in merge requests.

requested review from @mrzv

assigned to @vbolea

@vbolea Sounds neat. Where can I read more about it? And how does spack come into play?

@tpeterka You are probably interested in this too.

We can access the UO Frank CI gitlab runners through the Spack CI. Will you be interested to have build that tests in diff arch such as arm64 and ppc64?

I don't really understand what Spack CI does; I think that's my problem.

As for architectures, arm64 may be worth it, but I can't imagine needing ppc64.

resolved all threads

Do: merge

mentioned in commit 999aab93

merged manually

resolved all threads