ci(ci.sh): fix Docker Compose presence check - migrate to sub-command

[petermetz]

1. The old way to use docker compose was through the standalone binary
   docker-compose
2. This was working for a while but now the auto-upgrades that we cannot
   seem to avoid have caught up with us and broke ci.sh in the GitHub action
   runners because the standalone binary is no longer available at all and
   therefore the migration must happen.
3. Point 2 is just a theory but one that is considered to be very likely
   correct.
4. It is to be seen if we'll have any other downstream issues such as the
   tests failing in other ways due to this underlying docker change.

Signed-off-by: Peter Somogyvari [email protected]

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[jagpreetsinghsasan]

LGTM