⚠️ Remove aliyun provisioner from vc-manager

[christopherhein]

User Story

As an operator I would like to separate provisioning from configuring VC to configure clusters so that I can individual manage components based on responsibility.

Detailed Description

With the move away from provisioning in VC and the addition of CAPI support #81 we should draw a harder line about the responsibilities of the vc-manager, instead of being responsible for provisioning it should shift to responsible for maintaining the VC state backed by any Cluster object, this means we have to remove the native provisioned #131, as well as the aliyun provisioner, expecting VC to just maintain cluster stability from a CAPI CR.

Anything else you would like to add:

This likely needs support to make sure clients previously using it get the same expectation and have a new provisioner route.

/kind feature
/milestone next

[christopherhein]

/hold

[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