Added test workflow to install builded wheels before the upload

[jakub-kocka]

Description

• Added/Fixed unit tests and made them automatically run on PR
• Added installation tests for built wheels before upload to Espressif's PyPI
  • Also, another layer of exclusion mechanism is added for the dependencies of dependencies - everything that we have actually built is again verified with the exclude_list and removed from the packages which will be uploaded
  • Merged wheels in the repair step of the workflow to actually test platform-independent wheels on all platforms and Python versions in the test step
• Introduced architecture resolver for exclude_list.yaml
• Added text eclude builds to run on every PR - this will help us to keep exclude_list.yaml updated
• Added another verification workflow that runs on every PR to actually check what is uploaded in the S3 and if there are exclude list "violations" - might be from manual wheels upload (highly likely not complete wheel) ... this check also runs after the upload of main builds to check if we have not uploaded anything that we don't want to

Related

• internal tracker: IDF-14066

Testing

Unit tests: https://github.com/espressif/idf-python-wheels/actions/runs/21480882896/job/61876690271?pr=58
Action run platforms-dispatch: TBD
Action run defined-wheel: TBD

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[github-actions]

	Messages
📖	You might consider squashing your 4 commits (simplifying branch history).
📖	This PR seems to be quite large (total lines of code: 2019), you might consider splitting it into smaller PRs

👋 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.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- 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 92f2d75