[Feature Request]: Add macOS wheels (arm64 / universal2) for torch-mlir dev releases

Following the documented install command:
pip install --pre torch-mlir torchvision
--extra-index-url https://download.pytorch.org/whl/nightly/cpu
-f https://github.com/llvm/torch-mlir-release/releases/expanded_assets/dev-wheels
fails with:
ERROR: Could not find a version that satisfies the requirement torch-mlir (from versions: none)
ERROR: No matching distribution found for torch-mlir

MacOS on Apple Silicon is a common local development environment for PyTorch users evaluating or contributing to torch-mlir. Without published wheels, the only options are building from source or moving to a Linux/Windows host, which is a significant barrier for evaluation and CI on Mac-based developer machines.
Please restore macOS to the set of platforms for which nightly/dev wheels are published. macOS universal2 wheels were published in the past (see #1544), but the current release automation produces only Linux (x86_64 + AArch64) and Windows (x86_64) builds. For now, a macosx_*_arm64 (Apple Silicon) wheel would cover most current Mac hardware; a universal2 build would additionally cover Intel in a single artifact.

History / related issues:
#1544 (2022) — macOS universal2 torch-mlir wheels were published, but the matching torch dependency wheel for Mac arm64 was missing, breaking dependency resolution. A maintainer noted the blocker was CI / macOS-SDK tooling (waiting on GitHub Actions macOS runner updates, wanting SDK 11 support).
#2126 (2023) — On Intel macOS 13.x, the universal2 wheel was rejected as "not a supported wheel on this platform" (a cp311 tag / Python-version mismatch), and the package index failed to resolve torch-mlir at all. Shows the install path was unreliable on both Mac architectures.
#4275 (2025) — On Apple Silicon, install now fails outright with No matching distribution found for torch-mlir: no macOS wheel is published anymore.

Environment:
macOS: 26.5.1 (build 25F80)
Architecture: arm64 (Apple Silicon)
Python: 3.11.7
pip: 26.1.1
Suggested wheel target: cp311-cp311-macosx_11_0_arm64 (or universal2). Building against a macosx_11_0 minimum means a single wheel installs across all current macOS versions; my environment accepts both the arm64 and universal2 variants of that tag.
Compatible wheel tags pip accepts (abbreviated):
cp311-cp311-macosx_26_0_arm64
cp311-cp311-macosx_26_0_universal2
...
cp311-cp311-macosx_11_0_arm64
cp311-cp311-macosx_11_0_universal2
cp311-cp311-macosx_10_16_universal2
... down to macosx_10_9_universal2

Start by tracing the release automation that currently produces the Linux and Windows dev wheels, then inspect its macOS runner and SDK configuration. Add macOS arm64 or universal2 coverage and verify that the documented pip install resolves a cp311 wheel on Apple Silicon; confirm the resulting artifact is published with the dev-wheel release assets.