feat(platform-api): multi-audience JWT + Partner CRUD + tenant lifecycle (O.2)

JwtAuthGuard now accepts a comma-separated AUTHENTIK_AUDIENCE
('dezky-portal,dezky-operator'). jose.jwtVerify takes an array and succeeds
on any match — both customer-portal and operator-portal tokens validate
against this service. Per-endpoint guards restrict further.

New OperatorGuard enforces operator-only mutations:
  1. JWT audience claim includes 'dezky-operator' (proof from the token
     alone that this is a privileged session)
  2. ActorService-resolved User has platformAdmin=true (DB check so
     revocation works without waiting for the token to expire)
Both required; either alone is insufficient.

Partner module:
  - Partner schema: slug, name, domain, status, marginPct, contactInfo,
    billingInfo. marginPct is one number per partner (decided in grilling)
  - CRUD endpoints under @UseGuards(JwtAuthGuard, OperatorGuard) — every
    partner mutation requires operator scope
  - GET /partners returns each row with a computed customers count from
    aggregating Tenant.partnerId. MRR aggregation deferred until
    Subscription gains a price column
  - GET /partners/:slug/tenants for the partner detail view
  - DELETE soft-terminates (status='terminated') — never hard-delete
    because tenants may still reference the partner

Tenant changes:
  - partnerId?: Types.ObjectId (ref Partner, indexed sparse) added to
    Tenant schema
  - UpdateTenantDto accepts partnerId so PATCH can attach/detach
  - POST /tenants/:slug/suspend and /resume — operator-only via
    OperatorGuard. PATCH already covers plan/domains/partnerId changes

Smoke test: customer-portal session sends POST /api/partners through the
portal proxy → 403 "This endpoint requires an operator-scoped token". The
positive test (operator-token → 200) waits for O.3 when there's an
operator app to mint the right token.

apps/portal/server/api/partners/index.post.ts is a temporary verification
proxy — delete once the operator portal exists.

infrastructure/docker-compose/docker-compose.yml

@@ -411,7 +411,10 @@ services:
       OCIS_API_URL: https://files.dezky.local
       # JWT validation against Authentik for portal-issued access tokens
       AUTHENTIK_ISSUER: https://auth.dezky.local/application/o/dezky-portal/
-      AUTHENTIK_AUDIENCE: dezky-portal
+      # Comma-separated list of accepted JWT audiences. Tokens issued for either
+      # the customer portal or the operator portal are valid against this service;
+      # per-endpoint guards further restrict operator-only mutations.
+      AUTHENTIK_AUDIENCE: dezky-portal,dezky-operator
       AUTHENTIK_JWKS_URI: https://auth.dezky.local/application/o/dezky-portal/jwks/
       # Trust mkcert root CA for Node fetch (dev only)
       NODE_EXTRA_CA_CERTS: /etc/ssl/mkcert-root.pem