Add Linux aarch64 (arm64) build to release tarballs

[zoravar08]

The install script at https://agents.hyper.space/api/install currently maps platforms as:

linux-x86_64    -> aios-cli-x86_64-unknown-linux-gnu.tar.gz
darwin-arm64    -> aios-cli-aarch64-apple-darwin.tar.gz
darwin-x86_64   -> aios-cli-x86_64-apple-darwin.tar.gz
*               -> exit 1 "Unsupported platform"

There is no aios-cli-aarch64-unknown-linux-gnu.tar.gz asset, so any Linux arm64 host (Raspberry Pi 4/5, Oracle Ampere A1 Free Tier, AWS Graviton, NVIDIA Jetson, Apple Silicon under Linux VMs, Pine64, Rockchip dev boards, etc.) fails immediately with:

[-] Unsupported platform: linux aarch64

Why this matters

• Oracle Cloud's free tier offers 24 GB RAM Ampere A1 arm64 VMs — an obvious low-cost host for a Hyperspace daemon, currently locked out.
• AWS Graviton instances are the cost-leaders for always-on inference workloads.
• Edge / home-lab Pis are exactly the demographic likely to want passive Pod participation and the "always-on daemon VMs" the docs describe.

Ask

Add aios-cli-aarch64-unknown-linux-gnu.tar.gz (and ideally aios-cli-aarch64-unknown-linux-musl.tar.gz) to your release artifacts, and add the matching linux-aarch64 / linux-arm64 case to install.sh.

Environment tested

• Raspberry Pi 5, 8 GB — Ubuntu 24.04.4 LTS aarch64, kernel 6.8.0-1048-raspi
• Oracle Ampere A1, 4 vCPU / 23 GB — Ubuntu 24.04.4 LTS aarch64

Happy to test pre-release builds.

[zoravar08]

Concrete fleet impact in my own homelab — out of 4 Linux machines I'd want to run Hyperspace on, 3 are aarch64 and locked out:

Device	Arch	RAM	GPU
Raspberry Pi 5	aarch64	8G	—
Oracle Ampere A1 #1 (moviebee)	aarch64	23G	—
Oracle Ampere A1 #2	aarch64	23G	—
Windows laptop (WSL2)	x86_64	16G	RTX 3060 Laptop 6GB

Two of those arm64 boxes are 24G Oracle Ampere A1 Free Tier instances — exactly the kind of always-on Pod daemon host the project pitches. A Linux arm64 release tarball would let me run a real Pod across this fleet instead of a single-node Pod on the Windows GPU box.