Launch ControlePlane in existing cluster

**User Story**

As a user/operator, I would like to launch cluster master in kubernetes; it'll avoid additional provider (only provider for the worker node) and save cost by container/pod.

**Detailed Description**

Currently, I'm using Metal3 provider to manage workers; but it's cost concern to use bare-metals for master and it's complex to set additional VMs, e.g. BYOH ( https://metal3.io/blog/2022/07/08/One_cluster_multiple_providers.html ). So I'd like to manager cluster master in current k8s cluster by introducing a new ControlPlane.

**Anything else you would like to add:**

Here's an implementation (only kube-apiserver) at https://github.com/openbce/kink , I'd like to work with community to move forward.

/kind feature

Start with the CAEP process in CONTRIBUTING.md and review the linked kink implementation, which covers kube-apiserver. Define the proposed ControlPlane scope and acceptance criteria for launching a cluster master in the existing Kubernetes cluster while Metal3 manages workers; the issue does not identify project files or tests.

Written by the indexing model from the issue text.