Support `--profile` flag in "Compose Path" option for compose deployment

What problem will this feature address?

Background:
When one compose file supports multiple service configurations, the docker compose spec recommends profile groups to specify which services should run in which contexts.

Problem:
Dokploy supports this call signature already, but doesn't auto-populate discovered services under the "domains" tab.

Describe the solution you'd like

Dokploy would identify the active --profiles as it parses the compose file, so that the services dropdown list is in sync with the run command.

Describe alternatives you've considered

Dokploy could simply show all services present in the dockerfile, with warning text saying something like "CLI flags detected in compose path; these services may not be correct". This still has less margin for user error than a complete freeform services field enabled in #2273

Additional context

This situation arises when docker compose apps can optionally build on either the CPU or GPU, but not both:

# Snippet from docker-compose.yml
services:
  cpu-image:
    build: ...
    profiles: [cpu]
  gpu-image:
    extends: cpu-image
    runtime: nvidia
    profiles: [gpu]
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              device_ids: ["0"]
              capabilities: ["gpu"]

So that users can run docker compose --profile gpu up for respective app and hardware.

Will you send a PR to implement it?

Maybe, need help

The relevant entry points are the Compose Path option and the domains tab; start by tracing how the compose file is parsed and how its services populate the dropdown. Done means active --profile values are honored by the service list and match the docker compose run command, including the CPU/GPU example.