fix(ui): scope deployment delete loading

[azizbecha]

What is this PR about?

This PR scopes deployment deletion loading states to the deployments being removed. Previously, the mutation's shared pending state was passed to every delete button, causing all rows to show a spinner. A set of in-flight deployment IDs now lets concurrent deletions independently add and clear their own loading state.

Screen.Recording.2026-07-31.at.2.27.01.PM.mov

Checklist

• 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. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Testing

• pnpm --filter=dokploy typecheck
• pnpm exec biome check apps/dokploy/components/dashboard/application/deployments/show-deployments.tsx
• git diff --check

Issues related (if applicable)

Closes #4945

Screenshots (if applicable)

N/A

Greptile Summary

The deletion loading state now tracks deployments independently.

• Stores all deployment IDs with active deletion requests in a Set.
• Adds an ID when deletion starts and removes only that ID when it settles.
• Shows the loading state exclusively on the corresponding deployment’s Delete button.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; each deletion now removes only its own deployment ID from the loading-state Set, so one request settling cannot clear another deployment’s pending indicator.

_{Reviews (2): Last reviewed commit: "fix(ui): track concurrent deployment del..." | Re-trigger Greptile}