Add a short high-level explanation of typical docker-compose use cases

[VNel]

Docker-compose is widely used, but the documentation currently jumps very quickly into configuration details without clearly explaining typical real-world use cases.

A short, high-level section such as “When to use docker-compose” could help users better understand:

• in which scenarios docker-compose is a good fit (e.g. local development, testing, small setups)

• when other tools (plain Docker commands or Kubernetes) might be more appropriate

This would improve onboarding and reduce confusion for users who are new to container orchestration.

Definition of Ready (DoR):

• The contribution is documentation-only

• The section stays high-level and does not introduce new features

• No changes to existing behavior or configuration are required

• The goal is clarification, not technical depth

[snuweb]

I can add a short “When to use Docker Compose” section near the beginning of the docs to explain common real-world use cases (local dev, testing, small setups) and when plain Docker commands or Kubernetes may be a better fit. I’ll keep it high-level and docs-only