Add Python 3.13 support

[jakub-kocka]

Description

• Updated pre-commit hooks and mypy dependency (all-types is "staged in time" and sub-dependencies has been deleted)
• Added Python 3.13 support
• Updated exclude list - some wheels build not working for Python 3.13 (gdbgui, windows-curses)
• Added Print requirements job for the Python depended wheels for better debugging

Related

• Internal tracker IDF-11363
• Yet not supported gdbgui Python 3.13 is not supported cs01/gdbgui#494
• Yet not supported windows-curses Add Support for Python 3.13 zephyrproject-rtos/windows-curses#69
• cryptography issues on 32-bit ARM have been resolved by adding an environmental variable to not check the forward compatibility of ABI wheels (succeeded job - https://github.com/espressif/idf-python-wheels/actions/runs/11659438423/job/32461701157)

Testing

Succeeded job: https://github.com/espressif/idf-python-wheels/actions/runs/11347660297

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello jakub-kocka, 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 15a7457

[dobairoland]

@jakub-kocka Thanks, LGTM in general. What do you suggest how should we handle those new cases from the ignore list? We will have to get back to them later. If that period is too long then in the meantime we need restrictions on the ESP-IDF side.

[dobairoland]

You can use cs01/gdbgui#494 in your comments as tracker.

[jakub-kocka]

@jakub-kocka Thanks, LGTM in general. What do you suggest how should we handle those new cases from the ignore list? We will have to get back to them later. If that period is too long then in the meantime we need restrictions on the ESP-IDF side.

@dobairoland, thanks for the review. I have seen that you have added a message about gdbgui not supported with Python 3.13.

I think we can also update the constraints repository with the cases from the ignore list, this should prevent IDF from demanding a specific version for Python 3.13 if needed.

Can we merge this?

[dobairoland]

You can use cs01/gdbgui#494 in your comments as tracker.

You haven't linked this issue.

Here is the one for windows_curses: zephyrproject-rtos/windows-curses#69

Maybe this it the one for cryptography: pyca/cryptography#11436

The Windows and the cryptography ARM32 incompatibilities are serious ones and we need to track them internally to get back to this later.