📝 Update README and pyproject.toml with current supported Python versions

[github-actions]

Summary

This PR automatically updates README.md and pyproject.toml with the current supported Python versions based on our dynamic version detection system.

Changes Made

• ✅ Updated "Supported Python versions" section in README.md
• ✅ Updated ruff target-version in pyproject.toml
• ✅ Updated mypy python_version in pyproject.toml
• 🔄 Based on ESP-IDF lifecycle and Python EOL dates
• 🤖 Generated by automated workflow

Python Versions Updated

The following Python versions are currently supported:

["3.13","3.12","3.11","3.10","3.9","3.8"]

Verification

• Python versions in README match our build matrix
• pyproject.toml ruff target-version uses oldest Python version
• pyproject.toml mypy python_version uses oldest Python version
• No other sections of files were modified
• All supported versions are actively maintained

---

Note: This PR was automatically created by the update-python-versions workflow.
The Python versions are dynamically determined based on ESP-IDF support lifecycle.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello github-actions[bot], we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 0b36cd4

[jakub-kocka]

The PR creation looks good after the fixes have been applied, but we don't want to merge the Python 3.8 change because of the mypy checks. I am closing this.