install latest openfe and gufe as a canary to catch upstream changes

[mikemhenry]

No description provided.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0d59001) 82.74% compared to head (95415ea) 82.74%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   82.74%   82.74%           
=======================================
  Files          22       22           
  Lines        2735     2735           
=======================================
  Hits         2263     2263           
  Misses        472      472           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dotsdl]

Looks great @mikemhenry! Sorry for the delay in reviewing this one! Feel free to merge if satisfied!

[dotsdl]

Actually, think this runs into the same problem that prompted #203: installing new openfe dependencies, such as kartograff in this case, that aren't required by the most recent release.

I don't know of a good workaround for this.

[mikemhenry]

Suggested change

	run: pip install --no-deps git+https://github.com/OpenFreeEnergy/gufe git+https://github.com/OpenFreeEnergy/openfe
	run: |
	pip install --no-deps git+https://github.com/OpenFreeEnergy/gufe git+https://github.com/OpenFreeEnergy/openfe
	mamba install kartograff

[mikemhenry]

This should fix the issue highlighted here #204 (comment)
We have to manually install packages to make the canary pass, that way we can "catch" the upstream change. We can also not do that and just have the CI fail until a new openfe releases comes out and fixes the dependency issue