Refactor CAPZ codebase to reenabled kubebuilder

[nawazkh]

/kind cleanup

What needs cleanup:
[A clear and concise description of what needs to be cleaned up.]

• Refactor CAPZ code to reenable kubebuilder.

Describe the solution you'd like

• Following the mini experiment at Update PROJECT file #5390 (comment), we should probe to restore kubebuilder <command> functionality in CAPZ.
• If not restore, document the reason for moving away from Kubebuilder.
• If not moved away, we should try refactoring CAPZ code to leverage kubebuilder. I was not able to generate a new API in CAPZ (kubebuilder create api) without manual refactoring of CAPZ code.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale