fix(service): close edit domain modal after successful save

[devrim-1283]

Changes

• Fixed the service "Edit Domains" modal staying open after a successful save. Editing a domain on a service container (e.g. one that requires a specific port) saved correctly, but the modal never closed.
• Root cause: the component saved and refreshed but never dispatched the close-modal event the modal wrapper listens for. I dispatch it on the success path only, so the domain-conflict and required-port dialogs still behave as before — matching how the app's other modal forms close.

Issues

• No existing issue found — searched open and closed issues and PRs. Reproduces on a service container's "Edit Domains": enter a valid domain, click Save, save succeeds but the modal stays open.

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Preview

Before: the service "Edit Domains" modal stayed open after saving. After: it closes once the domain is saved.

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: Claude Code (credited as co-author on the commit)
• How extensively: It helped trace the root cause, wrote the one-line fix and the tests, and repaired the pre-existing test setup. I reviewed every change and ran the tests myself.

Testing

• Extended the service edit-domain test to run in isolation (database refresh, current-team session, base instance settings, the server's auto-created destination) and added a missing factory the file already referenced.
• New cases: modal closes after a save and after a confirmed port removal, and stays open while the port warning shows.
• php artisan test tests/Feature/Service/EditDomainPortValidationTest.php — 11 passed.

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.