Add explicit support for Python 3.11

[ricardoV94]

Depends on next Numba release for support of Python 3.11: numba/numba#8304

Not testing Numba on Python 3.11 for now

The last two commits of this PR should be removed once:

1. Numba supports Python 3.11
2. The mypy issue mentioned below is sorted out

---

Other unrelated CI changes

1. Don't run both fast-compile and float32 to reduce a big chunk of the tests combinations. Both modes are arguably very specialized on their own, and if we need tests to check their interaction we should add them explicitly. In general, the biggest issue with float32 is some Ops that would upcast stuff to float64. Fast-compile has less optimizations / introduces less specialized Ops, so this should be less of a concern for maintaining float32.
2. Exclude fast-compile/float32 from the oldest supported Python version. Run them on the newest instead.

[ricardoV94]

Other than numba and #238 tests seem to be passing in 3.11

CI is failing in 3.11, somehow mypy thinks that:

[pytensor/link/c/exceptions.py]
pytensor/link/c/exceptions.py:1: error: Module "setuptools._distutils.errors" has no attribute "CompileError"

I see that mypy is not officially supported in Python 3.11 yet, so maybe it will be sorted out once it is? python/mypy#12840

[codecov-commenter]

Codecov Report

Merging #198 (b590aca) into main (c28db53) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##             main     #198     +/-   ##
=========================================
  Coverage   80.43%   80.44%             
=========================================
  Files         170      170             
  Lines       45328    45328             
  Branches     9687    11069   +1382     
=========================================
+ Hits        36461    36463      +2     
+ Misses       6643     6642      -1     
+ Partials     2224     2223      -1     

see 2 files with indirect coverage changes

[ricardoV94]

Anything we need to do on the conda-forge side?

[michaelosthege]

Anything we need to do on the conda-forge side?

According to the current build status badge under https://github.com/conda-forge/pytensor-suite-feedstock/ and the files under https://anaconda.org/conda-forge/pytensor/files it's already outputting 3.11 artifacts.