feat(registry): add AWS ECR registry support with proper validation

[EphraimHaber]

• Add AWS ECR as a new registry type alongside existing cloud registries
• Implement ECR-specific authentication using AWS credentials instead of username/password
• Add conditional validation schemas that require different fields based on registry type:
  • ECR: registryUrl, awsAccessKeyId, awsSecretAccessKey, awsRegion
  • Regular: username, password
• Create executeECRLogin helper function for centralized ECR authentication logic
• Update both frontend and backend validation to use superRefine with field-specific error messages
• Fix apiCreateRegistry schema to make username/password optional for ECR registries
• Add proper shell escaping for security in all registry login commands

Backend changes:

• Update registry database schema to include AWS ECR fields
• Add getSafeECRLoginCommand and getSafeDockerLoginCommand helper functions
• Modify apiTestRegistry to handle ECR authentication flow
• Update registry services to use centralized login command generation

Frontend changes:

• Add ECR-specific form fields (AWS credentials, region)
• Implement conditional form validation matching backend logic
• Update registry creation/testing UI to handle ECR workflow

This enables users to connect to AWS ECR repositories using their AWS credentials while maintaining backward compatibility with existing Docker registries.

What is this PR about?

Please describe in a short paragraph what this PR is about.

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.

Issues related (if applicable)

closes #2040

Screenshots (if applicable)

[EphraimHaber]

Important Note

AWS CLI Required: The server running Dokploy needs AWS CLI installed for ECR authentication

[EphraimHaber]

just rebsed and orginized the commit

[EphraimHaber]

Cool, I'll fix these issues. Hopefully I'll have time for it tomorrow night.

[EphraimHaber]

fixed the issues. awaiting CR @Siumauricio

[vslowslow]

Any update？

[shivam-clary]

Upvoting for this to be reviewed and merged. Would be really helpful and make our deployment processes straightforward

[shivam-clary]

Would really appreciate if this PR could be a bit more prioritized. This has been open for more than 6 months and fixes a key pain point while using dokploy on AWS. Please request you to take a look at this @Siumauricio (sorry for tagging, but just wanted a bit of attention on this PR)

[Siumauricio]

Hi, Sorry for the late reply, can you please create a dedicated branch as we describe in the https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request, also can you fix the conflicts?

[EphraimHaber]

Sure, hopefully I'll have time to work on it later today.

[EphraimHaber]

@Siumauricio had some nice ui/ux changes in mind, went ahead and made a dedicated branch with screenshots included. #4141