`sim-setup status` shows Postgres and Redis as absent when they're running in the Compose stack

[Rajkumar2002-Rk]

After a Quick setup with sim-setup 1.0.28 on macOS, npx sim-setup status prints:

postgres (sim-postgres):  absent
redis (sim-redis):     absent
app (:3000)       ✓
realtime (:3002)  ✓

Both are actually up and healthy. docker ps shows sim-<project>-db-1 and sim-<project>-redis-1, which is how Compose names them.

It looks like detectContainer in packages/sim-setup/src/detect.ts matches the exact names sim-postgres and sim-redis, which only exist for standalone containers. Looking up the Compose project's db and redis services instead (for example by the com.docker.compose.project and com.docker.compose.service labels) would fix it. As it is, a first-time user sees "absent" next to their database and assumes setup failed.

Related, smaller: running npx sim-setup stop from a different directory prints "No Sim install detected. Run npx sim-setup first." That reads like an instruction to install again, when the real fix is to run it from the parent of the sim/ folder.

[AYANscyy2]

I'd like to take this. Plan: leave detectContainer as-is (its managed flag drives start/stop of standalone containers) and have status look up each Compose install's db/redis services by the com.docker.compose.project + com.docker.compose.service labels, same approach as configuration-sources.ts. I'll keep the 'stop from another directory' message as a separate PR.