Add macOS ARM64 CLI lab lane

[lefoulkrod]

What changed

• add a Darwin ARM64 release-contract and hardware lane for the physical VM-lab Mac host
• exercise the attended PTY installer and TUI while explicitly excluding Podman setup from the ready-runtime test profile
• cover dashboard, details, logs, settings, update cancellation, stop/start, Doctor, agent review/removal, JSON/config/update behavior, and an unattended lifecycle
• prepare the CLI archive and ARM64 container fixture off-host, then copy only final test inputs to the constrained Mac
• make terminal-driver waits resilient to output that arrives before a later screen refresh
• document the macOS lane, evidence, isolation, and manual remainder

Why

The release lab did not have an automated Darwin ARM64 consumer lane. The new physical-host backend in omnideck-dev/vm-lab#2 provides the lease and reset boundary; this PR adds the CLI/TUI consumer that runs against it.

Impact

A release qualification can now prove the native macOS ARM64 CLI archive and actual PTY workflows on Apple Silicon without modifying the user's long-lived CLI configuration or personal Podman resources.

Validation

• rebased onto current origin/main
• bash -n on the added and modified hardware/E2E scripts
• python3 -m unittest tests/e2e/test_lab_contract.py
• python3 -m py_compile tests/e2e/terminal_driver.py
• full macOS CLI/TUI evidence passed: /mnt/data/VMs/omnideck-release-lab/artifacts/cli/macos-e2e/20260814T023256Z-3665105
• canonical aggregate passed: /mnt/data/VMs/omnideck-release-lab/artifacts/macos/aggregate/20260814T023256Z-3665073

Dependency

• Drafted after and intended to consume Add native macOS ARM64 lab lane vm-lab#2.