playbooks: quiet down pip noise in TTS build logs

Profiling the index-tts deploy log (2057 lines) showed ~25% was just
pip's per-package Downloading / Collecting / Requirement-already /
progress-bar spam — useless for ops, hard to scan when something
actually breaks.

Three changes across the four TTS deploy playbooks:

1. Pulls (Kokoro): add --quiet. 6.5 GB pull no longer floods the log
   with per-layer progress redraws. Final "X Pulled" still prints.

2. Builds (VibeVoice, Chatterbox, IndexTTS-2): add --progress=plain
   to stop the BuildKit TUI from littering the captured log with
   carriage-return overdraws, then pipe through a grep filter that
   drops pip's noisy lines but keeps:
     - buildkit step transitions (#NN [stage])
     - DONE / CACHED / ERROR markers
     - apt + build-stage messages
   set -o pipefail keeps a real build failure from being swallowed
   by the grep's exit code.

Net effect: ~25% smaller logs, much more scannable; full visibility
into step progress and errors preserved.

playbooks/deploy-chatterbox.yaml

@@ -61,7 +61,11 @@ steps:
   # ── build + bring up ────────────────────────────────────────────────
 
   - name: docker compose build (~8-10 min first time; cached after)
-    shell: cd {{ compose_dir }} && docker compose build
+    # See deploy-vibevoice.yaml for the rationale — same filter pattern.
+    shell: |
+      set -o pipefail
+      cd {{ compose_dir }} && docker compose build --progress=plain 2>&1 \
+        | grep -vE '^#[0-9]+ [0-9.]+ (Downloading|Collecting|Requirement|Using cached|Installing collected|Successfully (installed|built)|Saved /|━|Resolved|Prepared|Built)'
 
   - name: docker compose up -d
     shell: cd {{ compose_dir }} && docker compose up -d