Make go/v4-alpha and kustomize/v2-alpha to be stable and the default CLI scaffold

[camilamacedo86]

What do you want to happen?

The following is what needs to get done:

• : check if we can move forward and get this one merged: ⚠️ go/v4-alpha: change the layout to follow Golang Standards #2985
• : check if we can close as deferred: Make better use of kustomize bases #615 (convey added on the issue)
• : release as alpha. Then, ask for the community to check it out (if significant issues are found, we need to release it as beta)
• : make the plugins stable and update the docs to no more extended reference it as alpha ⚠️ (go/v4-alpha) stabilize go/v4 plugin. Plugin go/v4-alpha replaced with go/v4 #3237 and ⚠️ (kustomize/v2) Stabilize plugin. kustomize/v2-alpha was replaced with kustomize/v2 #3234
• : make the plugins stable and make them the default CLI scaffold ✨ : make go/v4 to be default Kubebuilder CLI scaffold #3278
• : update readme and quick start since now we will support darwin/arm64 by default, and we do not need to say for people use go/v4-alpha anymore
• : deprecated go/v3 and kustomize/v1 - ⚠️ (kustomize/v1) deprecated v1 version in favor of v2 #3235 and ⚠️ (go/v3) deprecate go/v3 in favor of go/v4 #3238
• : deprecated packages to let consumers informed ✨ (API) deprecate kustomize/v1 and go/v3 packages #3284
• : update tutorials to use go/v4 📖 Update Component config tutorial to use go/v4 plugin #3280, 📖 update cronjob tutorial sample to use go/v4 #3281, 📖 update multiversion tutorial to use go/v4 #3282

Extra Labels

No response

[joejulian]

There are operators that have been built using upstream controllers. Moving these controllers to internal breaks downstream projects.