Retire IPClaim and IPAdderess CRDs in favour of CAPI provided IPAddressClaim and IPAdderess

[peppi-lotta]

User Story

Ip-Address-Manager is created for Cluter-Api-Provider-Metal3. As a user when I deploy CAPM3 with IPAM there are two types of ip claims (ipclaims.ipam.metal3.io and ipclaims.ipam.metal3.io) and two types of ip addresses (ipaddresses.ipam.metal3.io and ipaddresses.ipam.cluster.x-k8s.io). As a user I don't need two sets of CRDs that provide the same functionality and find it confusing that that there are two resources with the same name.

As a developer I don't want to uphold code base that provides same functionality for two almost identical CRDs. Because CAPI has added support for IPAMProviders there i work to make this IPAM into a provider. It is logical to use CAPI provided CRDs and reduce duplicacy.

Detailed Description

CAPI has added support for IPAMProviders and I have started work on making this IPAM into an official provider for CAPI. The ipClaim and IPAddress CRDs in this project can be retired and CAPI ipAddressClaim and ipAddress CRDs should be used in stead. Both projects CRDs are very similar and there is no point in having both.

/kind feature

[Rozzii]

/triage accepted
Accepted means that we can start the discussion in the community.
I would like to ask you @peppi-lotta to present the "plan" related to this issue in one of the community meetings too.
There are questions e.g. related to the usability of IPAM without CAPI.