Native shard merge drops the v0.30.0 macOS Mint binary

Follow-up to #1029.

`release/scripts/merge-release-native-platform-shards.py` removes `mint-{tag}-macos-arm64` from the roster at `>= (0, 30, 0)`. `merge-release-binary-shards.py` and `registry-release` stop listing Mint only after 0.30.0 (`> (0, 30, 0)`). v0.30.0 shipped `mint-v0.30.0-macos-arm64`, so re-merging its native shards with current tooling would omit that asset.

- [ ] Use `> (0, 30, 0)` in the native script
- [ ] Add a 0.30.0 case to `release/scripts/test_release_native_platform.py`

Also cover historical image onboarding (Codex thread PRRT_kwDOTEV0gs6h2oGw): the current v0.30.0 image roster retains Mint, but current-tree onboarding validation expects its retired Dockerfile, staging recipe and advisory baseline. Historical versions need inputs resolved from their versioned source instead of requiring retired Mint build inputs on current main.

- [ ] Verify v0.30.0 image onboarding against its historical source inputs.
- [ ] Keep current-version Mint retirement intact and preserve historical manifests and the VERIFY roster.

Inizia da release/scripts/merge-release-native-platform-shards.py e release/scripts/test_release_native_platform.py, confrontando le condizioni di v0.30.0 con merge-release-binary-shards.py e registry-release. Poi traccia la convalida dell’onboarding delle immagini e i relativi input sorgente storici. Il lavoro è completato quando v0.30.0 conserva il binario macOS Mint e i manifest delle immagini e VERIFY rimane valido, mentre il ritiro di Mint nella versione corrente resta invariato.

Scritto dal modello di indicizzazione a partire dal testo della issue.