fix: prevent orphaned containers when deleting compose services

[Siumauricio]

Summary

• Fixes composeType: "compose" deletion leaving orphaned containers and volumes running
• Commands were chained with &&, so if the project directory was missing, cd would fail and docker compose down would never execute
• Uses ; to run each command independently, matching the existing stack deletion pattern from PR fix: prevent orphaned docker stacks when compose directory is missing #3692

Closes #4064

Greptile Summary

This PR fixes orphaned containers left behind when deleting compose services (composeType: "compose"). The root cause was that commands were chained with &&, so if the project directory didn't exist, the cd would fail and docker compose down would never execute. The fix replaces && with ; so each command runs independently, and removes the now-unnecessary cd and cwd option since docker compose -p <project-name> down can identify containers by their project label without needing the compose file in the working directory. This aligns the behavior with the existing stack deletion pattern introduced in PR #3692.

Confidence Score: 5/5

Safe to merge — the fix is minimal, correct, and mirrors the established pattern for stack-type deletion.

The change is a targeted fix: replacing && with ; ensures docker compose -p down always runs even when the project directory is absent. docker compose -p down correctly identifies containers via project labels without a compose file. rm -rf with the -f flag silently succeeds on non-existent paths, so there are no new error surface areas. All findings are P2 or better.

No files require special attention.

Vulnerabilities

No security concerns introduced by this PR. Note that compose.appName is interpolated directly into shell commands, but this is a pre-existing pattern unchanged by this diff.

_{Reviews (1): Last reviewed commit: "fix: prevent orphaned containers when de..." | Re-trigger Greptile}