use `docker compose config` to support more compose features, like `include`

What problem will this feature address?

I've raised this topic several times already (#2441 #2455) but with some more clarification probably it can move somewhere)

docker compose support some useful features like include, merge, etc, with are extremely useful with more complicated projects. But dokploy currently doesn't support any of these, because just reads provided compose file and builds all machinery (variables, services, domains, etc) around it.

Describe the solution you'd like

In previous discussions was mentioned that parsing compose files and implementing complicated chaining is out of scope of dokploy, which is valid point, however this is not required at all, because docker already provides required tooling: config command

Essentially it does all the parsing and feature support and outputs a ready-to-use final compose. So to improve the support of compose deployments one thing is required: simply pass the compose through config command and use it's output to build the service machinery around.

Describe alternatives you've considered

In #2455 in discussion we figured out that in terms of include something could be danced around with custom -f arguments, but it is complicated and unreliable and most features will not work properly

Additional context

Would be happy to make a PR, but currently so overloaded that no chance I could properly dive in to project's code to make things good =(

Will you send a PR to implement it?

No

The issue names no files or tests. Start by locating where Dokploy reads Compose files and builds variables, services, and domains, then trace how a Docker Compose config command could supply the resolved output. Done means Compose features such as include and merge are resolved before the service machinery is built.