feat: Support docker compose CLI

[EricsonMacedo]

Check if docker compose v2, CLI, is available and get semantic version
from it, or fallback to get semantic version out of docker-compose v1
when checking minimum requirements during install.sh script

Fixes #962

[BYK]

Hi @EricsonMacedo thanks a lot for the patch!

I think we need the following to get this patch landed:

1. Fix the version check logic so we don't fail on 2.0.0+
2. Make sure we use docker compose instead of docker-compose by replacing $dc accordingly
3. Add a test case into the test matrix for Docker Compose 2.0

[PMExtra]

Please note that: I met some trouble in docker compose with sentry-onpremise.
The first, the install output format will be wrong. They cannot wrap line correctly.
Then when I used docker compose to make a clean install, I cannot make any interaction with the initialization script (It won't take any response, just like without -i / --interactive flag.

I have tested in several weeks ago with my own patch, with Docker version 20.10.8 and Docker Compose version v2.0.0-rc2 in a SSH session of CentOS 8.

[BYK]

@PMExtra does this patch address some of the issues you had? Btw they released v2.0.1 recently.

[aminvakil]

v2.0.1 can be used like before (docker-compose) and there is no need to specifically use docker compose.

So do you think this PR should be reverted (most parts) and using two different approaches for versions < 2 and >=2 would bring confusion for maintaining this repository or not?

[EricsonMacedo]

v2.0.1 can be used like before (docker-compose) and there is no need to specifically use docker compose.

So do you think this PR should be reverted (most parts) and using two different approaches for versions < 2 and >=2 would bring confusion for maintaining this repository or not?

@aminvakil Setting docker-compose binary isn't mandatory, it's an additional compatibility bin/symlink for transition period https://github.com/docker/compose-switch/. In v2 the command to output version isn't docker-compose --version as before and the output pattern is different as well.