Remove controller-runtime dependency

[XudongLiuHarold]

What would you like to be added?

Currently, cloud provider vsphere has sigs.k8s.io/controller-runtime package dependency which could be a potential blocker for the future release.
Because if we rely on controller-runtime, we can only support new k8s version by waiting until the controller-runtime supports it, it significantly slows down our process to release to support new k8s version.

Why is this needed?

Therefore, we need to remove the controller-runtime encapsulation and use client-go directly in our cloud-provider-vsphere repo.

Following files need to be refactor using client-go:

• pkg/cloudprovider/vsphereparavirtual/instances_test.go
• pkg/cloudprovider/vsphereparavirtual/instances.go
• pkg/cloudprovider/vsphereparavirtual/loadbalancer_test.go
• pkg/cloudprovider/vsphereparavirtual/vmoperator.go
• pkg/cloudprovider/vsphereparavirtual/zone_test.go
• pkg/cloudprovider/vsphereparavirtual/zone.go
• pkg/cloudprovider/vsphereparavirtual/types.go
• pkg/cloudprovider/vsphereparavirtual/vmservice_test.go
• pkg/cloudprovider/vsphereparavirtual/vmservice.go
• pkg/cloudprovider/vsphereparavirtual/fake_client_wrapper.go

Tasks

Beta Give feedback

1. Remove controller-runtime dependency in paravirtual mode code #841
   +0
   
2. Remove controller-runtime dependency in unit tests #842
   +0

[XudongLiuHarold]

/assign @XudongLiuHarold @DanielXiao

[XudongLiuHarold]

I found that all the places using controller-runtime is calling each other, so it is meaningless to split it into sub-tasks, I will use one for tracking logic code and another for testing