⚠️ Remove ClusterVersion from vc-manager & native provisioner.

[christopherhein]

User Story

As a user I would like to reduce the overall components deployed for using CAPN w/ VC so I don't need to support deprecated provisioning routes.

Detailed Description

With the move to support CAPN, provisioning should be done outside of VC drawing a hard line between CAPN and VC, with this move we'll be able to get vc-manager and the controller-gen manifests back to being auto generated and easily consumed.

Anything else you would like to add:

This should help to remove cruft that made #62 and #63 hard to configured and causes user confusion.

[Miscellaneous information that will assist in solving the issue.]

/kind feature
/milestone v0.1.x

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[christopherhein]

/remove-lifecycle stale
/lifecycle frozen