Feature Request: Automatically start stopped database services before backup restore

What problem will this feature address?

Description

When restoring a database backup, Dokploy currently requires the database container to already be running.

If the container is stopped, the restore process fails because the restore command only searches for running containers.

As a result, the restore fails with a generic Command execution failed error, which does not clearly indicate that the database service is simply stopped.

Describe the solution you'd like

Proposed functionality

Before executing a restore, Dokploy should:

1. Check whether the database service is running.
2. If it is stopped, start the service automatically.
3. Wait until the database is ready to accept connections.
4. Execute the restore.
5. Display clear progress and error messages during the process.

Describe alternatives you've considered

Suggested workflow

Restore requested
      ↓
Check database service status
      ↓
Is the service running?
      ↓
No → Start service
      ↓
Wait for database readiness
      ↓
Execute restore
      ↓
Display result

Additional context

No response

Will you send a PR to implement it?

No

Start at the restore command and the database service lifecycle handling; the payload does not name specific files or tests. Trace how stopped database containers are discovered and how restore commands are executed. Done means a stopped service is started, readiness is awaited, restore proceeds, and progress or failure messages clearly describe each stage.