Implement support for kubeadm v1beta3 types

[fabriziopandini]

User Story

As a user I would like CAPI to use latest kubeadm API types when possible

Detailed Description

kubeadm is going to introduce v1beta3 API types during the v1.22 release cycle, and at the same time, drop v1beta1 types.

CAPI should follow these changes.

Anything else you would like to add:

Feasibility of dropping support for v1beta1 types should be evaluated according to the outcomes of the discussion on #4444

/kind feature

[vincepri]

/milestone v0.4

[vincepri]

/area api

[fabriziopandini]

v1beta3 merged in kubeadm so, initially as a clone of v1beta2, we can start to work on this and get all the scaffolding (*) in place.
This will make easier to apply following changes to the API as they land incrementally in kubeadm

(*) scaffolding includes

• having a kubeadm v1beta3 API clone under bootstrap/kubeadm/types
• having all the conversion in place
• having the new v1beta3 used for kubernetes >= 1.22 in https://github.com/kubernetes-sigs/cluster-api/blob/master/bootstrap/kubeadm/types/utils.go

[ghost]

/assign
/lifecycle active

[davideimola]

Hi @fabriziopandini can you change the assignee to this user instead of @imoladavide?
I have commented with the wrong account!

[sbueringer]

/assign @davideimola

[vincepri]

/unassign @davideimola

@shysank Are you able to take care of this?

[vincepri]

/priority important-soon

[shysank]

/assign

[CecileRobertMichon]

/kind release-blocking