Fix version menu

[mikemhenry]

I've seen this problem in a few different repos, lets see if I can get lucky an unpining sphinx works

[mikemhenry]

This didn't fix things but the openff docs are working, so I just need to check what they are doing

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a6393f5) 82.21% compared to head (05e5787) 81.78%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #231      +/-   ##
==========================================
- Coverage   82.21%   81.78%   -0.44%     
==========================================
  Files          24       24              
  Lines        2964     2964              
==========================================
- Hits         2437     2424      -13     
- Misses        527      540      +13     

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

[mikemhenry]

This PR resolves #230 see:
https://alchemiscale--231.org.readthedocs.build/en/231/

[mikemhenry]

@dotsdl ready for review!

[dotsdl]

Thanks @mikemhenry! It's a shame things keep breaking with later and later sphinx versions, but I'm happy to take anything that works on this front! Really appreciate you diving into this one!

[dotsdl]

@mikemhenry it looks like our doc builds may now be failing following this merge: https://readthedocs.org/projects/alchemiscale/builds/23305648/

However, from the log output for the sphinx build, it isn't clear to me at all what the failure is. Do you see anything that stands out to you?

[mikemhenry]

Not sure what caused the change, but the problem is these warnings:
/home/docs/checkouts/readthedocs.org/user_builds/alchemiscale/checkouts/latest/docs/user_guide.rst:487: WARNING: external py:class reference target not found: gufe.protocols.Protocol

I can take a look

[dotsdl]

@mikemhenry that appears to be a warning, and @ianmkenney reports that he can't reproduce the failure locally. Any other insights as to why readthedocs may be issuing a failure here?

Otherwise, I may just revert this change to get docs building again, even if we don't have the version menu working.