[Sites] Deployment marked "Active" and "Ready" but router returns router_deployment_not_found (both custom domain and native appwrite.network preview URL)

### 👟 Reproduction steps 1. Have a Site on Appwrite Cloud with a custom domain configured, domain rule type set to "Active deployment" (e.g. mercadolaw-front.cobradevs.xyz). 2. In the Deployments list, delete several older deployments. 3. Trigger a new deployment (manual deploy from a Git branch, e.g. `test`) and wait for it to finish building — status shows "Ready". 4. Activate that deployment — it shows the green "Active" dot in the Deployments list. 5. Visit the custom domain in a browser (incognito, hard refresh), or click "Visit" on the deployment detail page (the native `*.appwrite.network` preview URL). 6. See error. ### 👍 Expected behavior The site should serve the content of the deployment currently marked "Active" — both via the custom domain and via the native `*.appwrite.network` preview URL. ### 👎 Actual Behavior Both the custom domain and the native `*.appwrite.network` preview URL return HTTP 404 with: {"type":"router_deployment_not_found","message":"This page is empty, activate a deployment to make it live.","code":404,"version":"0.9.44"} ...despite the deployment being marked "Active" and "Ready" (build succeeded in 1m11s, 9.74MB output — not an empty build). This also reproduces inside Appwrite's own embedded preview iframe in the console: both the deployment detail page and the site overview page show the "This page is empty, activate a deployment to make it live." placeholder for a deployment that is marked Active. Before deleting the old deployments, the custom domain was serving a *different, stale* deployment ID (visible via the `X-Appwrite-Deployment-Id` response header) than the one marked "Active" in the console, for 45+ minutes after activation. Requests to different edge nodes (nyc, mia, pdk) returned inconsistent `X-Edge-Rule-Cache` states (`hit` vs `miss`) for the same hostname at the same time — suggesting the domain→deployment routing rule is cached per edge node and not invalidated consistently on activation. Deleting the old depl…