Add docker compose deployment

[kevin-namba]

What this PR does / why we need it:
Enable developers deploy control plane on local single machine using docker-compose

Which issue(s) this PR fixes:

Fixes #4129

Does this PR introduce a user-facing change?:

Support deploy control plane by using docker-compose

[khanhtc1202]

LGTM with a nit. Any reason we have to store the docker-compose file in root? It mays confused our users that we only have docker-compose as the installer for pipecd. Do you guys have any idea to resolve that? 🤔

[kevin-namba]

LGTM with a nit. Any reason we have to store the docker-compose file in root? It mays confused our users that we only have docker-compose as the installer for pipecd. Do you guys have any idea to resolve that? 🤔

I think We have two ways

1. To store the docker-compose file in a directory under project root
   docker-compose name the project based on directory name that includes docker-compose.yaml, so we must name the directory a name such as "pipecd-control-plane"
2. To store the docker-compose file in root and edit Makefile
   Many developers use Makefile to deploy control-plane, so they do not take care of the files in root. But we should write rules to deploy via docker-compose in Makefile.

[khanhtc1202]

@kevin55156 okay, got it. Let's go with option 2 (since one more dir named pipecd-control-plane makes thing even harder to understand)

[khanhtc1202]

Temporary close; we need to reconsider making this part of the main repo or pushing to a different one.

[t-kikuc]

How about posting the example on PipeCD's official blog?

[t-kikuc]

I made PRs. These are useful for users.

• Examples: Add an example of local control plane by docker-compose #4822
• Blog: [blog] Add a blog of building a control plane on local by docker-compose #4823

[t-kikuc]

@kevin-namba
I posted a blog based on your gread idea and codes, thank you so much!
https://pipecd.dev/blog/2024/03/14/control-plane-on-local-by-docker-compose/