chore: Drop python 3.9

[hunner]

Pull Request Description

What and why?

Python 3.9 is EOL in October last year https://devguide.python.org/versions/ and the Test Python 3.9 with max dependencies github action job takes 22 minutes. So lets drop it.

How to test

None

What needs special review?

None

Dependencies, breaking changes, and deployment notes

None

Release notes

• Drop python 3.9 support

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

PR Summary

This PR removes Python 3.9 from the testing matrix and updates the project's python version requirement accordingly. The dependency testing YAML has been modified to test only Python versions 3.10 through 3.14, while the project's pyproject.toml has been updated to set the minimum supported Python version to 3.10. These changes ensure that the project only targets actively maintained Python versions, potentially improving maintenance and leveraging newer Python features.

Test Suggestions

• Run the full test suite on Python versions 3.10, 3.11, 3.12, 3.13, and 3.14 to confirm compatibility.
• Verify that installation and runtime behavior is as expected with the updated minimum Python version requirement.
• Ensure that any documentation referencing Python 3.9 is updated accordingly.

[hunner]

I think we should keep old python support as long as is feasible

From spencer