Multiple projects with the same service names does not work

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 https://github.com/jesseduffield/lazydocker/pull/774