fix(data-manager): wire OPENMAPX_COMPOSE_FILE into the container env

The E9 -f hardening reads process.env.OPENMAPX_COMPOSE_FILE in motis-import's create fallback, but the data-manager uses a curated environment block (no env_file: .env), so the var never reached the container. Add it to the manifest, derived from OPENMAPX_HOST_DIR — the repo is bind-mounted at the host path, so the generated compose is readable there and the path resolves identically inside the container, giving correct host bind-mount paths for docker compose -f up -d motis-staging.

Author: Medformatik

services/data-manager/service.json

@@ -21,6 +21,7 @@
       "OPENMAPX_ROOT_DIR": "${OPENMAPX_HOST_DIR:?OPENMAPX_HOST_DIR must be set — the data-manager container persists the Transitous lockfile (POST /transit/bump) via this path; see infra/docker/.env.example}",
       "OPENMAPX_CUSTOM_INTEGRATIONS_DIR": "${OPENMAPX_CUSTOM_INTEGRATIONS_DIR:-/app/custom_integrations}",
       "TSX_TSCONFIG_PATH": "${OPENMAPX_HOST_DIR:?OPENMAPX_HOST_DIR must be set}/tsconfig.base.json",
+      "OPENMAPX_COMPOSE_FILE": "${OPENMAPX_HOST_DIR:?OPENMAPX_HOST_DIR must be set}/infra/docker/docker-compose.generated.yml",
       "APP_API_BASE_URL": "${APP_API_BASE_URL:-http://app-api:3001}",
       "POI_INGEST_BOOTSTRAP": "${POI_INGEST_BOOTSTRAP:-true}",
       "UTMC_USERNAME": "${UTMC_USERNAME:-}",