Update minimum python version to 3.10 and add checks in CI

[ksivaman]

Description

We have a minimum python version requirement for our build (currently v3.8) but no way of checking whether new changes introduced violate this rule, e.g:

• [JAX] Add experimental internal used THD(packed) fused attn API #964 and [PyTorch] Add FP8 attention with current scaling #2012 used Structural Pattern Matching, support for which is only available from python 3.10 (pep).
• Several PRs also added the use of functools.cache as a decorator which is a 3.9+ feature.

Instead of changing the functionality to not use these features, I've taken the opportunity to update the minimum required python version to v3.10 since python v3.8 is at end of life (and v3.9 will also be by the end of the month) .

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

• Update minimum python version requirement to 3.10.
• Add python version requirements to the framework's setup.pys.
• Use a pre-commit hook to catch changes that violate the minimum version requirement.

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[ksivaman]

/te-ci

[ksivaman]

Pipeline 36220067

[timmoon10]

Version checks will be nice, but I'm uncertain how much we can rely on vermin. It's being developed by an individual, the last release was 2 years ago, and I'm unsure if it has had serious adoption by other projects. See this discussion from postmarketOS.

[ksivaman]

/te-ci

[ksivaman]

/te-ci