[Feature]: Support v1beta2 cluster schema

[alistarle]

Problem to Solve

ClusterAPI v1.11.0 introduce the v1beta2 schema: https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11

Despite the v1beta1 schema is now deprecated, it brings a huge feature which is the cross namespace clusterClass. Indeed, ClusterClass is an important feature to industrialize cluster creation, but in v1.10.0 it required for the template to be located in the same namespace, it's no longer the case in v1beta2 and v1.11.0 of capi.

Proposed Solution

Support the v1beta2 schema by following the upgrade guide of the cluster api documentation: https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11#how-to-bump-to-capi-v111-but-keep-implementing-the-deprecated-v1beta1-contract

Additional Context

Looks like this work has been already worked on some time ago here: https://github.com/outscale/cluster-api-provider-outscale/pull/239/files could it help the migration ?

Environment Details

- Kubernetes version (`kubectl version`):
- OS (`/etc/os-release`):
- Kernel (`uname -a`):
- cluster-api-provider-outscale version:
- cluster-api version:
- Install tools:
- Kubernetes distribution:
- Kubernetes distribution version:

[jfbus]

Thanks, I'll look into it and schedule the feature.

[jfbus]

#239 was an attempt at building a new CRD version for Osc resources. It has no relation with the cluster-api CRDs...

We will probably migrate in multiple steps, starting with changes having a minimal impact. Maybe keep using beta1 internally at first, as described in https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11#how-to-bump-to-capi-v111-but-keep-implementing-the-deprecated-v1beta1-contract.

A second step would migrate the provider to the beta2 contracts, and we would probably need to migrate to a new infrastructure schema version, based on the new infrastructure contract.

Migrating to a new schema would be the occasion of cleaning the Osc schema (removing unused fields, having a common VM definition for nodes and bastion, ...)