Add main muse2 branch to CI

[Aurashk]

As well as downloading the latest muse2 release for each OS in the CI and testing against them to make sure the notebooks still work, we also want to build the current main branch of muse2 and test against each build. We can likely follow a similar recipe to the muse2 ci script but doing seperate checkouts for the data analysis repo and the muse2 one.

Probably don't need to run cargo test because that should always be passing in main anyway?

[alexdewar]

As well as downloading the latest muse2 release for each OS in the CI and testing against them to make sure the notebooks still work, we also want to build the current main branch of muse2 and test against each build. We can likely follow a similar recipe to the muse2 ci script but doing seperate checkouts for the data analysis repo and the muse2 one.

Probably don't need to run cargo test because that should always be passing in main anyway?

Yep, we don't need to do cargo test -- we just need to build it. The way I'd do it is to install with cargo. You could do it from the git repo, specifying either main or the latest version as the rev, e.g.

cargo install --git https://github.com/EnergySystemsModellingLab/MUSE2 --rev main

# or
cargo install --git https://github.com/EnergySystemsModellingLab/MUSE2 --rev v2.1.0

I think this is worth doing, so I'm putting it in the next sprint.