feat: add docker compose include directive support

[TupiC]

Changes

• added support for "include" directive in docker compose files. they get resolved and replaced in the used files
• made use of git show to read the compose file from the object store: no longer need sparse-checkout, working tree or git version check since git show is available in all git versions
• i also added some unit tests for correct parsing and resolving

Issues

• Fixes [Bug]: Support include section for docker compose #2859 which got transformed to a discussion Support `include` section for docker compose #4049 : not only do these people need it, but I also think support for the include statement is a 'base' feature, since it has been available since docker compose version 2.20.3 and always using a workaround by replicating all services, volumes etc. in multiple docker compose files is laborious

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Preview

suppose we have the following docker-compose.yml

the frontend/docker-compose.yml looks like this:

the backend/docker-compose.yml looks like this:

the include paths would get resolved and the correct directives get injected in the main docker compose which looks like this (raw):

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: Cursor
• How extensively: unit tests + verifying the changes made in this PR

Testing

1. create a new resource in coolify (select public git repo)
2. use this git url https://github.com/TupiC/coolify-include-test/ (test repo for this PR)
3. set correct docker-compose.yml path
4. verify the include paths get replaced with actual docker compose contents (also for deployable compose)
5. deploy

also added unit tests for parsing and injecting

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.