chore(analytics): Umami-Kern entfernen — Injection, Client-Lib, Auth-Hook, Container, DB

Erster Schritt der Umami-Komplett-Entfernung (Entscheidung: kein Web-Analytics):
- hooks.server.ts: injectUmamiAnalytics-Injection raus (stoppt Script-Load in der Unified-App)
- packages/shared-utils/analytics-server.ts: GELÖSCHT (Script-Injection-Util)
- packages/shared-utils/analytics.ts: zu No-op entkernt — window.umami/isUmamiAvailable
  raus, trackEvent no-op; alle 28 *Events-Aufrufer kompilieren weiter (senden nichts)
- packages/shared-auth/authService.ts: inline-Umami-trackAuth-Hook + Aufrufe raus
- infrastructure/docker-compose.gpu-box.yml: umami-Service (mana-mon-umami) raus
- docker/init-db: CREATE DATABASE umami + GRANT raus
- gelöscht: docs/ANALYTICS.md, scripts/mac-mini/setup-umami-db.sh, picture-landing .env.example

VERBLEIBEND (separat, größer): ~60 weitere Dateien — 7 Landing-Layout.astro
(eigene Script-Injection), website-blocks Analytics-Feature, Legal/Datenschutz,
i18n×5, Admin-UI, ~20 Docs. Teils produkt-/rechts-sensibel → in Wellen.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

infrastructure/docker-compose.gpu-box.yml

@@ -80,24 +80,6 @@ services:
       retries: 3
       start_period: 60s
 
-  umami:
-    image: ghcr.io/umami-software/umami:postgresql-v2.18.0
-    container_name: mana-mon-umami
-    restart: unless-stopped
-    ports:
-      - '8010:3000'
-    environment:
-      DATABASE_URL: postgresql://postgres:${POSTGRES_PASSWORD}@192.168.178.131:5432/umami
-      DATABASE_TYPE: postgresql
-      APP_SECRET: ${UMAMI_APP_SECRET}
-      DISABLE_TELEMETRY: '1'
-    healthcheck:
-      test: ['CMD-SHELL', 'wget -q -O- http://127.0.0.1:3000/api/heartbeat || exit 1']
-      interval: 30s
-      timeout: 5s
-      retries: 3
-      start_period: 30s
-
   # ============================================
   # Photon Geocoder (pre-existing user container, adopted into compose
   # 2026-05-07 to gain a healthcheck). Backs mana-geocoding's