Modify the template generation logic for CAPV templates

/kind feature

Describe the solution you'd like Currently, the template generation code for kibe-vip based templates generates a ClusterResourceSet which installs the CPI/CSI on the workload cluster. The names of these resources created by the CRS are not dynamically generated. Hence if trying to reuse the same manifest template for different workload clusters results in the same secrets/config maps(used by the CRS) being updated. This could have unintended consequences when working with multiple clusters.

Anything else you would like to add: It would be great if we could prefix the resources with the name of the cluster to enable reuse of the same templates for different workload clusters.

Environment:

• Cluster-api-provider-vsphere version: n/a
• Kubernetes version: (use kubectl version): n/a
• OS (e.g. from /etc/os-release): n/a

/help /good-first-issue