BUG: docker-compose scan not including env

[JustNZ]

With #330 a new feature was introduced that allows to specify an docker-compose file outside the root of the repo. However when an env variable is required within the compose and I define the env within the Openship deployment configuration it still fails to scan the docker-compose fail.

Error: "Could not parse the Docker Compose file at "deploy/docker-compose": Set POSTGRES_PASSWORD in .env — must match database.password in backend-config.yaml"

So it seems like when Openship scans for the docker-compose it does not include the specified envs and so somehow fails.

[Rish-it]

Opened #407 for this.

Root cause: the wizard scan interpolates the Compose file against the repo .env alone (prepare.service.ts:780). Source and ResolveOptions carry no env, so the variables you set in the deploy configuration were never in scope when the file was parsed — and ${VAR:?message} is fatal to Compose when the variable is unset, hence the "could not parse" rather than a missing-value warning.

The parser already accepted explicit interpolation values (ComposeParseOptions.env); only the plumbing to reach it was missing. The PR threads it through and has the dashboard send what you have already entered when re-scanning a pinned compose path.

Reproduced with your exact layout — compose under deploy/docker-compose via the #330 pin, one required variable:

before: Could not parse the Docker Compose file at "deploy/docker-compose": Set POSTGRES_PASSWORD in .env
after:  services[db].environment.POSTGRES_PASSWORD === "s3cret"

A genuinely unset variable is still reported, so the #339 behaviour is unchanged.

@Hydralerne flagged a few scope questions in the PR description — notably three sibling callers of resolveProjectInfo with the same gap that I left alone pending your call on where project env should come from.