Disambigaute output path for Docker Compose deployments

[captainsafia]

Description
When generating Docker Compose projects, the project name is derived from the directory name rather than the full subpath. This causes collisions when multiple app hosts are deployed from directories that share the same parent folder name.

For example, Aspire uses aspire-output as the output directory for multiple app hosts. Since Compose relies only on the directory name, different app hosts end up deploying into the same Docker Compose project, which results in resource conflicts.

Expected Behavior
Each app host deployment should generate a distinct Compose project name, even when the output directories share a common parent folder. A unique identifier (e.g., a hash of the app host path or configuration) should be incorporated to disambiguate these project names.

Proposed Solution
Include the app host's unique SHA (or similar stable identifier) in the Compose project name to prevent collisions.