Separate CI tests for newest development versions and newest releases of dependencies

[Alexsp32]

Since some changes to NQCDynamics also require changes in dependencies such as NQCBase or NQCModels, there can be situations where the automated unit tests will not give useful results until a release of dependencies is made, which would then be incompatible with older NQCDynamics until that release is made.

Maybe it would make sense to run unit tests both on the newest releases of our dependencies, as well as on the newest commits of each to make concurrent releases of compatible versions of different NQCD packages easier.
(The alternative is running all unit tests locally, which is a pain)

[reinimaurer1]

How easy would it be to set this up on github actions? Sounds straightforward

[Alexsp32]

How easy would it be to set this up on github actions? Sounds straightforward

It would be a matter of modifying the existing CI settings slightly, but shouldn't be that hard. The main thing to keep an eye out for is that it would double the amount of runner usage.