feat: Move docker-compose file to the repo and use S3WAL mode by default

[sanks011]

Description

This PR addresses issue #2456 by moving the Docker Compose file from AutoMQ's CDN to the repository and configuring it to use MinIO with S3WAL mode enabled by default.

Changes

• Added docker-compose.yaml to the root of the repository
• Replaced LocalStack with MinIO as the S3-compatible storage backend
• Enabled S3WAL mode by default for improved performance
• Updated README.md with Docker Compose quick start instructions
• Added documentation for running AutoMQ locally using Docker

Key Benefits

1. Self-contained repository: No external downloads required, simplifies onboarding
2. Better developer experience: MinIO is widely used and easier to work with
3. Improved performance: S3WAL mode provides better durability and throughput
4. Improved documentation: New users can start with a one-step Docker Compose setup

---

Summary of Testing Strategy

• Local Docker Compose test: Successfully brought up the full stack using the new compose file
• MinIO verification: Accessed MinIO UI and verified buckets and file operations
• Broker testing: Brokers launched successfully with S3WAL mode enabled

---

Reference

This PR replaces the current setup:

curl https://download.automq.com/community_edition/standalone_deployment/install_run.sh | bash

With a repository-contained solution using docker-compose.yaml directly.

Fixes #2456

---

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[CLAassistant]

All committers have signed the CLA.

[daniel-y]

Cool, thanks for your contribution, I will review on it later.

[daniel-y]

Hi, @sanks011 , I assume you're familiar with the setup of Kafka or AutoMQ. I apologize for not providing more details earlier. Currently, the Docker Compose starts 1 controller and 2 brokers, which seems unusual and not ideal. Here’s a possible solution:

1. By default, start a single server node with MinIO for a quick start.
2. Provide another compose file to support deploying a three-server cluster with MinIO.

I know this is beyond the scope of the current issue, so it's fine to maintain the current setup, and we can review it later. However, if you're okay with it, adopting the above solution would be appreciated.

[daniel-y]

Great, I'll merge it and maybe add my polish after your pull request.

[sanks011]

Great, I'll merge it and maybe add my polish after your pull request.

Thank You!