Initial sketch to use Docker Compose instead of commands to manage containers

[Axodouble]

I created this draft with the following message in Discord before:

Restarted my server, traefik was up before the network was.
So Traefik crashed.
Dokploy instance was unreachable because of it.
So I attempted to fix it, long story short fixed it by removing all dokploy services and reinstalling it and keeping the files.

Decided to take a glance at Dokploy's installation, would it not work significantly better to use a docker-compose for the installation that is maintained separately that is pulled from the site too? Which then could be used by Dokploy itself to check its services health and if something fails to run docker compose again?

I decided to use curl to download the docker compose from the website. (Which is probably better to actually put in the main Dokploy repo, but for sake of ease I put it here now) and from there on use the docker compose file to enable / disable the services if they already exist.

This should fix issues that could occur when reinstalling the application or collisions with the name.

So here is the pull request, please review, and would love to hear feedback.

[Siumauricio]

Hello, I believe the compose you created is exactly the same as what we had in the script.

In fact, we do not perform any health validation to check if the services are running correctly. In this PR, for now, I prefer to stick with what we currently have. If I decide to change it in the future, I would take your idea into consideration.

Thank you