feat(docker): pull images with stored registry credentials

[AminDhouib]

Summary

Lets a Docker-source application reference a stored registry so its credentials are used to docker login before the image is pulled — instead of forcing inline username/password on the app. Applies to both deploy paths.

• packages/server/src/db/schema/application.ts: add registryId to the apiSaveDockerProvider input.
• apps/dokploy/server/api/routers/application.ts (saveDockerProvider): when a registryId is chosen, persist it and clear inline username/password/registryUrl; otherwise persist the inline credentials and clear registryId.
• packages/server/src/utils/builders/index.ts (getAuthConfig): for sourceType === "docker", resolve the selected registry's credentials for the Swarm authconfig.
• packages/server/src/utils/providers/docker.ts (buildRemoteDocker): resolve the selected registry's credentials for the remote docker login/pull.
• apps/dokploy/components/dashboard/application/general/generic/save-docker-provider.tsx: registry selector in the Docker provider form.

Ports Dokploy#3678 by @AceRRR10 (manual apply; upstream co-authored).

Adaptations

The fork's registry model differs from upstream, so this is a manual adaptation rather than a cherry-pick:

• Credentials loaded on demand. The fork deliberately excludes registry passwords from relational queries (registry: { columns: { password: false } }), so instead of reading registry.password off the loaded relation (upstream's approach), getAuthConfig and buildRemoteDocker fetch credentials via the fork's existing findRegistryByIdWithCredentials(registryId).
• Kept the fork's safeDockerLoginCommand for the remote login (upstream reverted to a raw docker login string).
• Skipped upstream's image-name auto-concatenation churn (commits that add then revert prefixing the registry URL onto the image): the fork's getImageName / uploadImageRemoteCommand already use the docker image reference as-is and getRegistryTag already lowercases, so upload.ts needed no change.

Notes

• Uses the existing registryId column and already-loaded registry relation — no database migration (this item's reserved slot 0186 stays unused) and no new relational query on applications.

Verification

• pnpm --filter=dokploy run typecheck passes on this branch.