Ambertools 22 on Python 3.11

[mikemhenry]

Ambertools 23 had a behavior change openmm/openmmforcefields#281 from ambertools 22 that is causing some issues downstream. If we had an ambertools 22 build for python 3.11 (osx-arm arch would be nice as well) then we could keep using ambertools 22 when python 3.10 drops out of NEP.

I am creating this issue to track problems that arise when trying to make a ambertools 22 build for python 3.11. We did try an python 3.11 build for ambertools 22 here #111 but decided to just add a python 3.11 build for ambertools 23.

[mattwthompson]

We should patch the repodata, yeah?

[mikemhenry]

sorry @mattwthompson I had this tab open to remind me to do that but now I can't remember what needs to be patched, I belive I updated the openmmforcefield package to not pull in ambertools23, is that the package you think needs patching? Or does Ambertools need a patch?

[mattwthompson]

I don't remember, but from this comment: OpenFreeEnergy/alchemiscale#252 (comment)

I believe we want all existing openmmforcefields builds to have ambertools <23 added in.

Since that concern cannot be addressed by changes here, I've opened an issue over there: conda-forge/openmmforcefields-feedstock#14

I think the main issue (that there are no AmberTools 22 + Python 3.11 builds) is unresolved so we should keep this open