Fix initialized status to respect cluster-api contracts

[lbrunOVH]

Hi,

In the cluster-api documentation, it says that the 'initialized' status should be set to true only when the control-plane has been contactable once.
However, currently we set 'initialized' status when the TenantControlPlane has its Status.Kubernetes.Version.Status not nil. (https://github.com/clastix/cluster-api-control-plane-provider-kamaji/blob/master/controllers/kamajicontrolplane_controller.go#L195)
Which means that when the TenantControlPlane is still in "Provisionning", we have already have set 'initialized' status before the deployment is ready.
I discovered this when I had an issue with my ETCD DataStore, the deployment was not yet created and the cluster-api was already trying to contact the APIServer.

Linked to cluster-api documentation/code about control-plane contract and the 'initialized' status:
https://cluster-api.sigs.k8s.io/developer/providers/control-plane#required-status-fields
https://github.com/kubernetes-sigs/cluster-api/blob/main/api/v1beta1/condition_consts.go#L74