[ci/python] Versions audits on Python CI files

[johnkerl]

Context:

• In order to reduce CI queueing times we don't run exhaustive CI on every PR push
• In particular:
  • Pre-merge "mininal" CI: https://github.com/single-cell-data/TileDB-SOMA/blob/1.8.0/.github/workflows/python-ci-single.yml
  • Post-merge "full" CI: https://github.com/single-cell-data/TileDB-SOMA/blob/1.8.0/.github/workflows/python-ci-full.yml
  • Shared code between them: https://github.com/single-cell-data/TileDB-SOMA/blob/1.8.0/.github/workflows/python-ci-single.yml
• Recent version changes:
  • Recently we dropped Python 3.7: [python] Drop 3.7 support #1790
  • Recently I (@johnkerl) bumped one of the subset CI jobs to run on 3.11 rather than 3.10
    • Rationale: single "minimal" CI runs on a few versions, try to run it on oldest and newest versions we support
    • No 3.12 for us yet: 1849
  • There's linting running only on 3.10 meaning this didn't run pre-merge anymore (which we very much want it to)
• @ryan-williams has already debugged and root-caused this (I'm typing up his findings)
• However lets see what else we missed -- FYI https://gist.github.com/johnkerl/8437c56ef32ca4c705ddb4752a27c777
• Related: [python] Typeguard not running as intended #2238

[johnkerl]

@ryan-williams you deep-dove some things here.

@jp-dark I know CI isn't your favorite but the auditing part I think would be a nice little warm-up task -- just take a look at which Python versions we're using for which CI YAML, probably bias toward 3.11 over 3.10, make them consistent. Should be quick I hope! :)