[Test] deps(compose): use compose v5

[ndeloof]

What does this PR do?

use compose SDK (docker/compose/v5) This is a sanity-check PR before compose v5.0.0 release

Why is it important?

This is the first release with official SDK support

[netlify[bot]]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	e5695189cbfb58cac83497ac7ab173f2b32dd20d
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-go/deploys/6915a13ba799560008d42188
😎 Deploy Preview	https://deploy-preview-3490--testcontainers-go.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai[bot]]

Summary by CodeRabbit

• Chores
  • Updated Docker Compose dependency from version 2 to version 5 to ensure compatibility with the latest upstream releases. No breaking changes to existing functionality.

Walkthrough

The PR updates the docker/compose module dependency from v2.40.2 to v5.0.0-rc.2, updating all corresponding import paths from docker/compose/v2 to docker/compose/v5 across Go source files, tests, and the Makefile.

Changes

Cohort / File(s)	Summary
Import path updates modules/compose/compose.go, modules/compose/compose_api.go, modules/compose/compose_api_test.go	Updated docker/compose import paths from v2 to v5 across multiple modules
Dependency version modules/compose/go.mod	Bumped docker/compose dependency from v2.40.2 to v5.0.0-rc.2
Build configuration Makefile	Updated compose-replace target to reference docker/compose v5 instead of v2

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• All changes follow a consistent v2-to-v5 upgrade pattern with no logic modifications
• Limited scope across imports and version specifications
• Key area for attention: verify compatibility between v2.40.2 and v5.0.0-rc.2; ensure no breaking API changes in the docker/compose package that could affect downstream behavior

Suggested labels

dependencies, compose

Poem

🐰 From v2 to v5, the compose module takes flight, Import paths refreshed, dependencies polished bright, A simple hop upward in versions divine, The rabbit approves—all updates align! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title 'use compose v5' accurately reflects the main change: upgrading docker/compose from v2 to v5 across all module files and dependencies.
Description check	✅ Passed	The pull request description clearly explains the changes (updating to compose v5 SDK) and provides relevant context about why it matters (first official SDK release).

✨ Finishing touches

• [ ] 📝 Generate docstrings

🧪 Generate unit tests (beta)

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}