swa deploy seems to get stuck on arm64

**Are you accessing the CLI from the default port `:4280` ?**

- [ ] No, I am using a different port number (`--port`) and accessing the CLI from that port
- [ ] Yes, I am accessing the CLI from port `:4280`
- [x] I am not using any port

**Describe the bug**
`swa deploy` seems to get stuck on arm64

**To Reproduce**
Steps to reproduce the behaviour:

1. Be on a arm64 system
2. Type in command 'npx swa deploy ...'
3. See application stuck somewhere after
```Deploying project to Azure Static Web Apps...
Fetching release metadata for version: stable. Please wait...
GET https://aka.ms/swalocaldeploy
Decode JSON:
Local client binary is up to date. Skipping download.
Deploying using /root/.swa/deploy/53b7d0e07fe5c34bf68929fab92f87ce910288dc/StaticSitesClient@53b7d0e07fe5c34bf68929fab92f87ce910288dc
Deploying using the following options:
- env:
```

(Same thing works on a x86-64 system)

**Expected behavior**
Ideally: swa deploy works on arm64
Better than nothing: swa deploy exits with an error on arm64

**System**

- Azure VM "Standard D4pds v6"
- Docker container based on `node:24`
- OS: `Debian GNU/Linux 12 (bookworm)`
- npm: `11.5.1`
- node: `v24.7.0`
- swa: `2.0.6`

**Additional context**
When manually starting StaticSitesClient, it reports `./StaticSitesClient: cannot execute binary file: Exec format error`
`file ./StaticSitesClient` reports `./StaticSitesClient: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=2c1e53af795f334d83be915591e65fee55966751, stripped`

Comienza con el comando `swa deploy` y sigue cómo selecciona o inicia el `StaticSitesClient` descargado; el informe muestra que el binario obtenido es x86-64 en arm64. Reproduce el problema con el entorno Debian arm64 `node:24` indicado y verifica que el despliegue funcione en arm64 o finalice con un error claro en lugar de quedarse bloqueado.

Escrito por el modelo de indexación a partir del texto del issue.