PR: Add Python 3.11 to CIs/tags & overhaul CI config

[CAM-Gerlach]

As discussed in #386 , adds official support for Python 3.11 (following a similar template to #296 which added 3.10 support) in the Trove tags and CI tests, making the necessary binding and Qt version adjustments as required for the 3.11 jobs, including a somewhat non-ideal but necessary workaround for a conda package solver incompatibility on Py311 + pyqt 5.15 + qt 5.15.

Along the way, I've refactored the CI config to centralize the binding and Qt API version selection all in one place in the matrix config, to greatly reduce duplication of version constants and the scattering of the logic multiple places in the declarative config and the dynamic execution script. In concert with that, I've been able to:

• Ensure that all four bindings have their lower (5.9/6.2), middle (5.12/6.3) and upper (5.15/6.2) bound versions tested on at least one CI job
• Fix an issue with most PySide 6.x jobs accidentally using the lower rather than the middle or upper bound version
• Unskip the macOS-Python3.7-pip job, as it now runs fine without errors
• Add the missing Qt version parameter to the conda install call for PySide6 and fix its indent (from PR PR: Try PySide6 on conda #378)
• Fix some other issues in test.sh, including a small but meaningful typo in a comment, an unnecessary pip spec/version, and a tab/spaces problem

I've also updated/fixed a few related small ancillary bits:

• Upgraded the checkout and setup-python action versions to the current
• Elided the redundant wheel build-time dependency
• Removed the deprecated license_file metadata key superceded by license_files

Fixes #386

[CAM-Gerlach]

@ccordoba12 @dalthviz I've apparently discovered a conda dependency solution issue that can be worked around here, but should probably be fixed properly upstream, most likely with a new release of the qt metapackage (which might in turn require a new release of qt-webengine). Specifically, no version of the qt metapackage and pyqt are mutually compatible on Python 3.11, and running

conda create -n test-env python=3.11 pyqt qt

or equivalently

conda create -n test-env python=3.11 pyqt=5.15 qt=5.15

fails on all platforms with a dependency resolution error, which you can see the full output of on CI in e.g. this run.

Specifically, I've traced the issue to following three incompatible constraints:

• The latest pyqt 5.15.7 is the earliest version supported on Python 3.11 (5.15.4 will not install)
• pyqt 5.15.7 requires qt-main, of which only 5.15.6 is mutually compatible with pyqt (5.15.4 is mutually incompatible, but will install on its own on Python 3.11, or with pyqt 5.15.7on Python <3.11)
• The latest version of the qt 5.15 meta-package is 5.15.4, which pins on qt-main and qt-webengine of the same point version

To note,

conda create -n test-env python=3.11 pyqt=5.15.7 qt-main=5.15.6 qt-webengine=5.15.4

does resolve. Also, 5.15.4 is the latest version of qt-webengine, though conda-forge/qt-webengine-feedstock#20 is open to update it to 5.15.7—though that wouldn't be in sync with the latest qt-main version, so I'm not sure if that can be pinned with qt unless qt-main is also updated to that version.

Should this be reported to one or more of those feedstocks? Or can something else be done about it?

[ccordoba12]

Should this be reported to one or more of those feedstocks? Or can something else be done about it?

I think it should be reported in the qt-feedstock to update the constraints it has on qt-main and qt-webengine.

[CAM-Gerlach]

Thanks, I've opened conda-forge/qt-feedstock#234 on there as suggested.

In the meantime, though, that doesn't block this PR, since I implemented a workaround (that's not quite as elegant as I'd like, but works just fine for now).

[ccordoba12]

A couple of small suggestions for you @CAM-Gerlach, otherwise looks good to me.

[ccordoba12]

Looks good to me now, thanks @CAM-Gerlach!

[dalthviz]

Thanks @CAM-Gerlach !