fix: resolve Portainer deployment Redis and CORS failures

Remove Docker Compose profiles from postgres and valkey services so they
start by default without --profile flag. Add NEXT_PUBLIC_APP_URL,
NEXT_PUBLIC_API_URL, and TRUSTED_ORIGINS to the API service environment
so CORS works in production.

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

docker-compose.yml

@@ -27,9 +27,6 @@ services:
       start_period: 30s
     networks:
       - mosaic-internal
-    profiles:
-      - database
-      - full
     labels:
       - "com.mosaic.service=database"
       - "com.mosaic.description=PostgreSQL 17 with pgvector"
@@ -58,9 +55,6 @@ services:
       start_period: 10s
     networks:
       - mosaic-internal
-    profiles:
-      - cache
-      - full
     labels:
       - "com.mosaic.service=cache"
       - "com.mosaic.description=Valkey Redis-compatible cache"
@@ -384,6 +378,10 @@ services:
       MOSAIC_TELEMETRY_API_KEY: ${MOSAIC_TELEMETRY_API_KEY:-}
       MOSAIC_TELEMETRY_INSTANCE_ID: ${MOSAIC_TELEMETRY_INSTANCE_ID:-}
       MOSAIC_TELEMETRY_DRY_RUN: ${MOSAIC_TELEMETRY_DRY_RUN:-false}
+      # Frontend URLs (for CORS and auth redirects)
+      NEXT_PUBLIC_APP_URL: ${NEXT_PUBLIC_APP_URL:-http://localhost:3000}
+      NEXT_PUBLIC_API_URL: ${NEXT_PUBLIC_API_URL:-http://localhost:3001}
+      TRUSTED_ORIGINS: ${TRUSTED_ORIGINS:-}
     volumes:
       - openbao_init:/openbao/init:ro
     ports: