ci: use v2 command for docker-compose

[emmettbutler]

This change updates the Github Action that uses docker-compose to call the appropriate command given the recent upgrade of that software on the ubuntu Action image described in actions/runner-images#9557. This had been leading to CI failures like this.

Checklist

• Change(s) are motivated and described in the PR description
• Testing strategy is described if automated tests are not included in the PR
• Risks are described (performance impact, potential for breakage, maintainability)
• Change is maintainable (easy to change, telemetry, documentation)
• Library release note guidelines are followed or label changelog/no-changelog is set
• Documentation is included (in-code, generated user docs, public corp docs)
• Backport labels are set (if applicable)
• If this PR changes the public interface, I've notified @DataDog/apm-tees.
• If change touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.

Reviewer Checklist

• Title is accurate
• All changes are related to the pull request's stated goal
• Description motivates each change
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Change is maintainable (easy to change, telemetry, documentation)
• Release note makes sense to a user of the library
• Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: emmett.butler/docker-compose-v2
Commit report: f4fbdf0
Test service: dd-trace-py

✅ 0 Failed, 82471 Passed, 90399 Skipped, 8h 44m 55.67s Total duration (3h 16m 1.37s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-04-02 21:03:02

Comparing candidate commit f9f3e8c in PR branch emmett.butler/docker-compose-v2 with baseline commit 1c1f54a in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 201 metrics, 9 unstable metrics.

[emmettbutler]

#8844