IPAM decoupled from CAPI Metal3 provider, starting from v1.10.0

We currently can't upgrade the metal3 operator (see !4332 (closed)) because, starting from v1.10.0, IPAM is now decoupled from the operator, therefore the IPAM CRDs are no longer installed.

For reference, see upstream MR https://github.com/metal3-io/cluster-api-provider-metal3/pull/1993

Helm install failed for release sylva-system/cluster with chart sylva-capi-cluster@0.10.0: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "mgmt-1873593499-rke2-capm3-virt-primary-pool" namespace: "sylva-system" from "": no matches for kind "IPPool" in version "ipam.metal3.io/v1alpha1"
         ensure CRDs are installed first, resource mapping not found for name: "mgmt-1873593499-rke2-capm3-virt-provisioning-pool" namespace: "sylva-system" from "": no matches for kind "IPPool" in version "ipam.metal3.io/v1alpha1"
         ensure CRDs are installed first]

( https://gitlab.com/sylva-projects/sylva-core/-/jobs/10371299182#L1207 )

We need to address this issue when we want to move from our current version. This should be done by installing IPAM as a separate unit.