Deleting a project leaves orphaned Secret Vault assignments

To Reproduce

When a project assigned to a Secret Vault is deleted, the associated Secret Vault assignment is not removed. The vault keeps a reference to the deleted project.
This causes subsequent attempts to edit the Secret Vault to fail with:

Steps to reproduce

1. Create a project, for example demo-project.
2. Create or configure a Secret Vault provider.
3. Assign the Secret Vault to demo-project.
4. Save the Secret Vault configuration.
5. Delete demo-project.
6. Open the Secret Vault configuration again.
7. Attempt to edit and save the provider, even if no meaningful changes are made.

Current vs. Expected behavior

Expected behavior

Deleting a project should also remove all Secret Vault assignments referencing that project.

Alternatively, the Secret Vault edit screen should automatically ignore or remove assignments pointing to deleted projects.

Current behavior

The deleted project remains in the Secret Vault assignment list. When the provider is updated, the API rejects the request with:

Assignment references a project outside this organization

This prevents the Secret Vault configuration from being edited through the UI.

Provide environment information

OS: Ubuntu 24.04
Dokploy Version: v0.30.6

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help

Reproduce the project deletion and Secret Vault editing workflow described in the issue, then trace the project-deletion path and the Secret Vault assignment update API. Done means deleting a project removes or safely ignores its assignments and the Secret Vault can be edited and saved without the organization-reference error.