Monitor failures in "Install from conda-forge" workflow with pint 0.24

[khaeru]

This run of the conda.yaml workflow failed today with messages like:

  File "/Users/runner/work/_actions/iiasa/actions/main/setup-conda/Anaconda3/envs/testenv/lib/python3.9/site-packages/pint/compat.py", line 19, in <module>
    from typing import (
ImportError: cannot import name 'TypeAlias' from 'typing'

Briefly what appears occurred is:

• pint 0.24 was released, bumping the minimum supported version of Python to 3.10. IOW, Python 3.9 is no longer supported.
• This version of pint was packaged for conda-forge, but without bumping the minimum Python version.
• That conda-forge package was installed in our workflow, which still uses Python 3.9. Notice at the first URL above the pint installed is pyhd8ed1ab_0, with _0 meaning this is the 0th version of the conda-forge recipe for this particular pint version.
• The conda-forge packaging issue was noticed and fixed; see Mark pint 0.24 build 0 requires Python 3.10 rather than 3.9 conda-forge/conda-forge-repodata-patches-feedstock#776 and Require Python 3.10 conda-forge/pint-feedstock#66.

FYI @glatterf42

I expect this issue will fix itself tomorrow, when the next workflow run should see pint 0.24 pyhd8ed1ab_1, which is already on conda-forge, and refuse to install it, preferring pint 0.23 for Python 3.9. We could then close this without doing anything.

Recording here only:

1. for posterity, and
2. because this made me notice we could maybe update to newer versions of *conda with newer Pythons for this workflow. This is, however, lower priority, since we now recommend the pip-based install.