refactor(crd): rewrite the RisingWave and the controller

[arkbriar]

Signed-off-by: arkbriar arkbriar@gmail.com

What's changed and what's your intention?

PLEASE DO NOT LEAVE THIS EMPTY !!!

Please explain IN DETAIL what the changes are in this PR and why they are needed:

• Rewrite the API structs according to the proposal RFC: a new design of RisingWave CRD #105 and refactor the controller manager
  • Rewrite the RisingWave and add a new CR RisingWavePodTemplate
  • Add a validating webhook for RisingWavePodTemplate to ensure immutability
  • Refactor the controllers and webhooks
• Provide several examples to demonstrate how to work with the new CRD
• Move the legacy APIs into the legacy directory
• Revise the readme and dev docs
• Misc things
  • Bump controller-gen to 0.9.2 to fix an issue
  • Bump ctrlkit-gen to latest to fix an issue
  • Re-generate the CRDs as well as the manifests
  • Embed the apis package in the outside package
  • Declare the CRs in categories all and streaming

Now you can view the RisingWave related resources with the following command:

k get streaming
NAME                                                               AGE
risingwavepodtemplate.risingwave.singularity-data.com/privileged   5s

NAME                                                               RUNNING   STORAGE(META)   STORAGE(OBJECT)   AGE
risingwave.risingwave.singularity-data.com/risingwave-etcd-minio   True      Etcd            MinIO             2m22s
risingwave.risingwave.singularity-data.com/risingwave-in-memory    True      Memory          Memory            2m9s
risingwave.risingwave.singularity-data.com/risingwave-privileged   False     Memory          Memory            5s

Guidance to review:

• The APIs under apis/risingwave/v1alpha1
• The object factory under pkg/factory
• The controller manager under pkg/manager
• The others are generally generated or modified passively

Checklist

• I have written the necessary docs and comments
• I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

[Nebulazhang]

Rest LGTM! Do you have tested on AWS cluster? I suggest testing it on local cluster and AWS cluster.

[Nebulazhang]

Why remove the Monitoring part?

[arkbriar]

It's generally not telling the truth, so I think it should be removed for now, especially the service monitor part. We can add it back to the readme after implementing it.