[BUG] : Container restart when using compose services

To Reproduce

1. Create a compose service using multiple containers. One service is an "init" container to setup a database for example and a main service with the restart always policy depends on the successful termination of this "init" service.
2. Physically restart the server
3. The main service is now offline and we need to retrigger a manual deployment to solve the issue.

Current vs. Expected behavior

The expected behaviors would be a restart of the physical server ensure that the deployments are running in the state they were running before the reboot.

Provide environment information

Dokploy Version v0.29.14
Debian 13
[Example of problematic deployment here](https://github.com/LouisPauchet/ThingsBoard_Dokploy_Deployment/blob/main/docker-compose.yml)

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

Docker Compose

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?

No

Start with the linked docker-compose.yml and reproduce the deployment after physically rebooting the Debian server, focusing on the init-container dependency and restart policy. Trace the Docker Compose deployment startup path in Dokploy; done means the main service automatically returns to the pre-reboot running state without a manual redeployment.