Domain binding should not require specifying port number for deployed services

What problem will this feature address?

When adding a custom domain to an already deployed project, Dokploy requires the user to manually enter the service port. This is redundant because the platform already knows the exposed port from the deployment configuration. It creates unnecessary friction, increases the chance of misconfiguration, and is confusing for users who expect domain routing to work automatically once a service is running.

Describe the solution you'd like

Dokploy should automatically infer the correct port from the deployed service when adding a domain. The port field should not be required in normal cases. If needed, the option to override the port can be placed under an advanced or optional setting.

Describe alternatives you've considered

Continuing to manually enter the port every time works as a workaround, but it is error prone and does not scale well for multiple services or less experienced users.

Additional context

This behavior differs from most modern PaaS platforms, where domain binding is handled automatically through the reverse proxy once a service is deployed. Improving this would significantly enhance the developer experience and reduce configuration mistakes.

Will you send a PR to implement it?

Yes

No files or tests are named in the issue. Start by tracing the domain-binding flow for an already deployed service and identify where the service's exposed port is stored and consumed. Done means the port is inferred in normal cases, remains optionally overridable, and domain binding still works for deployed services.