Review NEST Testing strategy

[heplesser]

With a view to testing what we aim/claim to support, we should review our testing strategy. Some points to consider are:

• How to cover different Linux Distributions and long-term support versions?
• How/if to cover different macOS versions?
• How/if to cover different hardware (e.g., Intel/Arm)?
• How to keep the compute/energy resources consumption for testing within bounds?

A challenge with testing for, e.g., package builds might be that Github seems to provide a lot of up-to-date software by default on their runners. Thus, the Ubuntu 20.04 runners we currently use, have CMake 3.29.2 installed (see https://github.com/actions/runner-images/blob/ubuntu20/20240422.1/images/ubuntu/Ubuntu2004-Readme.md), while Ubuntu 20.04 only provides CMake 3.16 (altough cmake-mozilla, whatever that is, apparently provides 3.27.

[github-actions]

Issue automatically marked stale!