What is this PR about?

Adds a per-compose-service Compose Profiles setting that activates one or more docker compose profiles at deploy time.

Only services tagged with a matching profiles: entry (plus services with no profile, which always run) are brought up. This lets users keep a single docker-compose.yml for multi-environment / multi-flavor stacks (e.g. dev vs gpu vs debug) and pick the slice they want to deploy from the Dokploy UI, without forking the file or overriding the run command.

The field is optional: empty value preserves the existing behavior (all services deployed).

Checklist

Before submitting this PR, please make sure that:

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Issues related (if applicable)

Screenshots (if applicable)