modify kuberay operator crds in kuberay operator chart and add apiserver chart

[scarlet25151]

Why are these changes needed?

Add a new chart for deploy kuberay apiserver

The crds in helm chart is generated by the controller gen in ray-operator folder by running make helm

Related issue number

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[Jeffwan]

I am thinking is it better to embed kuberay-apiserver in kuberay helm (remove kuberay-operator). Or keep it a separate chart? Ideally, we should move everything to single public chart #260

[scarlet25151]

Move the kuberay-operator to the subcharts of kuberay so we can use helm to deploy operator and apiserver at once use something like helm install kuberay ./kuberay without coupling two charts together.

[Jeffwan]

I feel it's better to keep kuberay-operator at this moment, once we finish the release and give the latest guidance, let's remove it. I know lots of user still use this folder and removing it will bring the breaking change.

Few things

1. Please leave a deprecation notice there.
2. Please update docs (README.md) and https://github.com/ray-project/kuberay/tree/master/docs/deploy
3. Please help fix it in original kuberay-operator folder [Bug] Missing rayservices.ray.io CRD access rules in ClusterRole #284

[scarlet25151]

I feel it's better to keep kuberay-operator at this moment, once we finish the release and give the latest guidance, let's remove it. I know lots of user still use this folder and removing it will bring the breaking change

@Jeffwan yes, indeed, here I need to confirm that if we keep kuberay-operator folder and then add the apiserverchart into it, we need to change the structure in values.yaml and path in /template to separate indicate operator's and apiserver's parameters like: opertor.resource and apiserver.resource it will bring some effort for coupling and decoupling the charts if we would put the two chart together for now.