Feature request: publish pre-built Android binaries as GitHub **Releases**

#### Context
The repository already has CI workflows under `.github/workflows/`, notably:

* **bpftools.yml** – builds `bpftools` / `bpftools-min` for `arm64` and `x86_64`
* **jdwp.yml** – builds the JDWP tracer
* **black.yml** – linter

`bpftools.yml` even uploads the resulting `bpftools-.tar.gz` via
`actions/upload-artifact@v4`.

That’s great 🎉 — but these artifacts are:

* **ephemeral** (default retention ≤ 90 days)
* **hard to discover** (buried under each workflow run)
* **not version-pinned** (no semantic tag or checksum)

---

#### Proposal

1. **Tag-triggered release**
Extend the existing workflow(s) to run on `push` **tags** (e.g. `v*`).
2. **Attach artifacts as Release assets**
Use `softprops/action-gh-release` or `actions/create-release` + `upload-release-asset` to upload:
* `bpftools-arm64.tar.gz`
* `bpftools-x86_64.tar.gz`
* (optionally) `bpftools-min-*`, static `bpftrace` binaries, checksums

Thanks for your reply in advance.