🌱 chore: cherry pick changes from 1.4.4 to 1.5.1

[cbuto]

What this PR does / why we need it:
Following what was done in #18. This is one part of https://d2iq.atlassian.net/browse/D2IQ-98202.

I cherry-picked the changes applied on top of 1.4.4 kubernetes-sigs/cluster-api@v1.4.4...mesosphere:cluster-api:v1.4.4-d2iq.0.

dropped the following commits:
727f1c2 - another fix for this was merged upstream in v1.5.0
7f84879 - this was also merged upstream in v1.5.0

Here is the migration guide: https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.4-to-v1.5

• We need to remove the LazyRestMapper feature gate
• It also looks like we reference v1alpha3 in a few places

Manually tested by:

• Created a bootstrap cluster
• built the images locally and updated the capi, kubeadm contollers, and capd deployments
  • I also had to remove the LazyRestMapper feature gate
• created three docker clusters

The first test I ran, the capi-kubeadm-bootstrap-controller-manager pod was OOMKilled once after creating a cluster. Subsequent tests with 3 clusters in a row didn't hit this.

[dkoshkin]

Thanks, Im excited for that list of commits to be going down 🥳

I also had to remove the LazyRestMapper feature gate

Is this s FF that was removed upstream?

[cbuto]

Is this s FF that was removed upstream?

@dkoshkin yup, it looks like we disabled it previously LazyRestmapper=false for some reason.

from https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.4-to-v1.5#removals

The lazy restmapper feature gate was removed in controller-runtime and lazy restmapper is now the default restmapper. Accordingly the EXP_LAZY_RESTMAPPER feature gate was removed in Cluster API.