Future plans for v1alpha1 APIs

[lentzi90]

CAPO has a few v1alpha1 types:

• OpenStackClusterIdentity
• OpenStackFloatingIPPool
• OpenStackServer

We should plan for what to do with these in the future. Ideally they should either evolve and be promoted to beta or be deprecated and dropped before too much time has passed.
I am creating this issue to track the plans for them.

OpenStackServer

This one is quite "easy". The goal should be to migrate to the OpenStackServer from ORC and we already have an issue for this: #2814

OpenStackClusterIdentity

We test this API in the e2e tests. It has already been with us for a few release cycles and similar patterns are used by other infrastructure providers. I think we should simply promote this up to beta and include it with the other "core" types.

OpenStackFloatingIPPool

This is the hardest. We do not use them in the e2e tests, so we don't have a good signal for if they are "working". CAPI has introduced an IPAM contract, but we do not implement that so we are on our own here. ORC has some floating IP features but not something equivalent to this.
I think our options are basically:

1. Switch over to a proper IPAM contract implementation, or
2. Document why we cannot/won't implement the IPAM contract and promote the API to beta instead, or
3. Deprecate and drop the API.