fix listing of services

[bosix]

What I did

Currently, when listing services in v2 (compose ps --services) only running containers are observed and listed since in the background the docker api is asked for matching containers. This pr fixes this behavior by using the full list of services provided by compose itself.

Since this is my first pr here, I would appreciate any feedback or ideas on how to better implement this. For example, I was thinking of a flag that would allow the user to select the desired behavior themselves, but since v1's service list was different, I just implemented the fix.

Related issue

The issue is described in #9391.

closes #9391

[ndeloof]

I'm not sure how compose v1 implements ps --services flag and what the initial intent was for this option, but if the intent is to just list services from compose model, then docker compose config --services command should be preferred.

[ndeloof]

answering my own question: this has been introduced by #5384, introduced to improve shell completion.

This change make this the exact same as docker compose config --services, while ps --services make sense because it reflect actual state of the compose application, so should be based on existing services, not just project model. i.e compose ps (--filter) return the status of a compose app, and --services option only shows involved services.

I don't have a strong opinion on the direction to choose here, maybe @glours @ulyssessouza ?

[glours]

As discussed with the team in charge of Compose, we think that the purpose of docker compose ps --services --all is to list running services of a compose stack (regular services and the ones started with oneoff containers) and not to listing project model services.
As mentioned you should use docker compose config --services to do that