Deployment fails with "content server communication" error — Azure SWA infrastructure issue

## Description

Azure Static Web Apps deployment is consistently failing with infrastructure-side errors across multiple retries. The build completes successfully but the deployment pipeline is unreachable.

## Environment

- **Region:** East US (or confirm yours)
- **Workflow action:** `Azure/static-web-apps-deploy@v1`
- **Deployment ID:** `0385cc24-aeff-4945-9382-cc53c1e53c49`
- **Date:** 2026-04-23

## What happens

Three consecutive failures with different error patterns, all Azure-side:

**Attempt 1** — fails during polling after upload (9 min):
Finished Upload. Polling on deployment.
Status: InProgress. Time: 537s
Deployment Failure Reason: Invalid API key.

**Attempt 2** — fails after upload:
We are currently experiencing problems communicating with our content server.

**Attempt 3** — fails before build even starts:
Looking for event info
We are currently experiencing problems communicating with our content server.

**Azure Portal** — also timing out when resetting deployment token:
Resetting token failed with the error: {"code":"ServerTimeout","message":"The request timed out.",
"tracking id":"e637de4a-316d-4f9b-9f30-6e029f767e48"}

## What was verified (not the cause)

- ✅ Build completes successfully (2003 modules, Vite)
- ✅ API token was reset in Azure Portal and updated in GitHub Secrets
- ✅ Workflow updated to `actions/checkout@v4`, OIDC removed
- ✅ TypeScript compiles without errors
- ❌ All failures are on Azure's deployment infrastructure side

## Expected behavior

Deployment should complete after upload finishes.