build 0.21.4 with armv7

[hfudev]

No description provided.

[Copilot]

Pull Request Overview

This PR creates a new GitHub workflow to build ARMv7 wheels for tree-sitter-c version 0.21.4. The workflow sets up automated building of Python wheels specifically for ARMv7 architecture using self-hosted ARM runners.

• Adds a new GitHub Actions workflow for building ARMv7 wheels
• Configures the workflow to checkout tree-sitter-c at version v0.21.4
• Sets up Python wheel building with cibuildwheel for native ARM architecture

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Python 3.8 has reached end-of-life status in October 2024. Consider upgrading to a supported version like Python 3.9 or later for security updates and continued support.

Suggested change

	python-version: "3.8"
	python-version: "3.9"

[github-actions]

	Warnings
⚠️	The Pull Request description is empty. Please provide a detailed description.

👋 Hello hfudev, 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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 b042325

[hfudev]

@dobairoland I succeeded with a custom action. Please don't merge this MR.

I tested the built wheel on armv7, and it's working. could you help upload it to our internal pypi server? Thanks a lot!

[hfudev]

the built artifact is here: https://github.com/espressif/idf-python-wheels/actions/runs/18041416522/artifacts/4116196054

[dobairoland]

@hfudev It should be done: https://dl.espressif.com/pypi/tree-sitter-c/