Multiple projects with the same service names does not work

[dougclayton]

Describe the bug
Lazydocker does not support "clones" of the same docker compose project, or any case where two projects share a service name.

To Reproduce
Steps to reproduce the behavior:
Make docker1 and docker2 directories, each with this compose.yaml:

services:
  sleep:
    image: ubuntu:latest
    entrypoint: ["/bin/sh", "-c"]
    command: ["echo 'Sleeping...' && sleep 100000"]
    stop_grace_period: 0s

Run docker compose create in each. Now run lazydocker in each. One of them will detect the other as the project and will not be able to manage the one in the current directory. Using an explicit -p does not fix this.

Expected behaviour
Both instances manage their own local project regardless of the service name.

Desktop (please complete the following information):

• OS: Ubuntu
• Lazydocker Version 0.25.2

Additional context
This was seemingly introduced in #774

[dougclayton]

Also, I just want to say how much of a fan I am of both lazydocker and lazygit, and of course I used lazygit to help make the PR! I really appreciate all your work on those two tools.

[groutoutlook]

I'm afraid the project has gone full hibernation though. for anyone interested in this PR and cant wait, you may want to apply the changes locally first then.