Fix runtime operations failing when env file is missing

[maxproske]

What I did

Closes #13135

Tolerate missing env file on runtime commands that should only depend on container labels like down, ps, logs, etc.

When an env file is deleted while a container is running, or an unused env file is declared by another service, most Compose commands fail, including docker compose down. Containers become unmanageable by Compose, and you must use docker down directly or recreate env files to bring containers down.

Note: This pattern likely affects other file dependencies like secrets.file and configs.file.

Steps to Reproduce

cat > compose.yaml << 'EOF'
services:
  app:
    image: alpine
    env_file: deleteme.env
EOF

touch deleteme.env

docker compose up -d

rm deleteme.env

docker compose ps
# env file /Users/max/dev/repro/compose-13135/deleteme.env not found: stat /Users/max/dev/repro/compose-13135/deleteme.env: no such file or directory

docker compose down
# env file /Users/max/dev/repro/compose-13135/deleteme.env not found: stat /Users/max/dev/repro/compose-13135/deleteme.env: no such file or directory

[ndeloof]

For commands that should only depend on container labels, one could pass project name, this disables compose.yaml file parsing.