Add docker registry credentials store and app-level selection

[prem-prakash]

/claim #2499

🎯 Partial Implementation: Docker Registry Credential Store

This PR implements the credential storage portion of #2499, providing a solid foundation for Docker registry authentication while deferring the image management UI to a future PR.

📦 What's Included

This PR addresses the credential store requirements from #2499:

✅ Credential Storage & Management

• Store Docker registry credentials (username, password, registry URL)
• Associate credentials with applications via application selector
• Secure password encryption (using Laravel's encrypted casts)
• UI for creating and editing registry credentials
• Ability to clear credentials (both username and password)

✅ Validation Improvements

• Fixed asymmetric validation where only one field would show errors
• Proper "both or neither" validation for username/password pairs
• Consistent error messages on both fields when incomplete
• Input trimming and empty string → null conversion

✅ Test Coverage

• 4 feature tests covering create/edit flows (DockerRegistryLivewireTest)
• 2 unit tests for deployment integration (ApplicationDeploymentJobDockerRegistryLoginTest)
• 6 tests total, 31 assertions - all passing ✅

🎥 Demo Video

Videos.Library.Loom.-.28.December.2025.fe45d731a47c49ee85c556ae5a9d62f9.mp4

🔧 Technical Changes

Backend:

• app/Livewire/Security/DockerRegistry/Create.php - Removed required_with validation, added explicit null checks
• app/Livewire/Security/DockerRegistry/Show.php - Fixed credential change validation to error both fields
• app/Models/DockerRegistry.php - Model-level trimming via booted() hook (already existed)

Tests:

• tests/Feature/DockerRegistryLivewireTest.php - Comprehensive Livewire component tests
• tests/Unit/ApplicationDeploymentJobDockerRegistryLoginTest.php - Deployment integration tests

📋 What's NOT Included (Future PR)

This PR intentionally excludes the image management UI portion of #2499:

❌ Deferred to Future PR:

• Docker image browsing/listing from registries
• Image tag selection UI
• Image search and filtering
• Interactive image selector component

🤔 Why Partial Implementation?

1. Smaller, focused PR - Easier to review, test, and merge (167 lines vs potential 500+)
2. Foundation first - Credentials are prerequisite for image management
3. Lower risk - Credential storage is well-defined; image UI needs UX discussion
4. Faster value - Users can start using private registries immediately
5. Iterative approach - Validate credential foundation before building complex UI

🚀 Immediate Value

Users can now:

• ✅ Store credentials for private Docker registries (GitHub Container Registry, Docker Hub, etc.)
• ✅ Authenticate with registries during application deployments
• ✅ Manage multiple registry credential sets per team
• ✅ Associate different credentials with different applications

📝 Testing

All tests passing locally and aligned with codebase patterns:

$ spin exec coolify php artisan test --filter "DockerRegistry"
PASS  Tests\Unit\ApplicationDeploymentJobDockerRegistryLoginTest
PASS  Tests\Feature\DockerRegistryLivewireTest
Tests:  6 passed (31 assertions)

Test coverage includes:

• Creating registries with trimmed credentials ✅
• Validation requiring both username and password ✅
• Clearing credentials (both fields) ✅
• Changing credentials with proper validation ✅
• Deployment integration when credentials present/missing ✅

🎯 Next Steps

After this PR merges, the image management UI (#2499 remaining portion) can be built on top of this credential foundation in a separate PR.

---

Related: Partially addresses #2499 (credential store only; image management deferred)

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}