Concurrent deployments are silently queued with no UI feedback

What problem will this feature address?

Title

Concurrent deployments are silently queued with no UI feedback

Description

When multiple applications are deployed at the same time, deployments are not executed concurrently. Instead, one deployment runs while others appear to be silently queued.

However, there is currently no visual or system feedback indicating that:

• The deployment is queued
• It is waiting for another deployment to finish
• Its current position in the queue

This creates confusion, as users may assume:

• The deployment did not trigger
• The system is stuck or unresponsive

Steps to Reproduce

1. Have multiple applications in Dokploy

2. Trigger deployment for more than one application simultaneously

3. Observe that:

   • One deployment starts immediately
   • Others do not start
   • No indication is shown that they are queued

Impact

• Poor developer experience
• Confusion during CI/CD workflows
• Difficult to debug deployment delays

Suggested Improvement

• Introduce a queue state in the UI
• Add real-time status updates via WebSocket or polling

Describe the solution you'd like

Expected Behavior

• Show clear deployment states such as:

  • "Queued"
  • "Waiting for available worker"

Actual Behavior

• No feedback is shown
• Deployment appears idle or stuck

Describe alternatives you've considered

None

Additional context

No response

Will you send a PR to implement it?

Yes

The issue names no files or tests. Start by tracing the deployment lifecycle and the UI's existing deployment-status updates, then inspect how concurrent deployments are represented and whether WebSocket or polling is already used. Done means queued deployments visibly show a queued or waiting state and update when execution begins.