Standardize naming

[chris-sun-star]

The naming in oceanbase resource types are too casual, the same resource are refreenced as different name in different resources, for example, clusterName in obcluster resource means the name of the cluster defined in oceanbase, and clusterName in obtenant resource means the corresponding obcluster resource in K8s.
This may be confusing to both users and developers, we need to keep the same rule for naming resources, this can be achieved by bumping the api version up and use the proper name for resources, kubebuilder provides the way to use multiple version of apis, so ideally there's no compatibility problem with old api resources.
refreence:
https://book.kubebuilder.io/multiversion-tutorial/conversion

[chris-sun-star]

I suggest to use the resource type to reference the custom resources and use xxxName as the name config of the resource
for example
obcluster means the obcluster resource, this is the name in Kubernetes
clusterName means the name of a obcluster, this is the config in OceanBase