fix(anisette): wait_for_rollout=false so a slow first start can't strand the deploy out of state

The docker.io fix created the deployment, but wait_for_rollout (default true)
then hung on the OOMing pod and the apply failed — leaving the deployment in
the cluster but NOT in terraform state, so every later apply hit
'deployments.apps "anisette" already exists'. Deleted that orphan and set
wait_for_rollout=false (mirrors tts/llama-cpp slow-start services); readiness
probe still gates Service traffic.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

stacks/anisette/main.tf

@@ -55,6 +55,12 @@ resource "kubernetes_deployment" "anisette" {
       tier = local.tiers.aux
     }
   }
+  # anisette downloads + initializes Apple's CoreADI provisioning library on
+  # first start (slow, memory-spiky). wait_for_rollout=false so the apply never
+  # blocks on — and never strands out of terraform state — a pod that is still
+  # warming up (mirrors tts/llama-cpp). Pod health is still gated by the
+  # readiness probe below, so the Service only routes once it's actually up.
+  wait_for_rollout = false
   spec {
     replicas = 1
     selector {