Feature parity with CAPO

[mandre]

What would you like to see implemented?

In order to use ORC controllers in CAPO, we need to match feature parity with what CAPO currently exposes. This issue is a top-level issue to track needed changes.

New controllers:

• [ ] KeyPair (https://github.com/k-orc/openstack-resource-controller/issues/136)
• [ ] Trunk (https://github.com/k-orc/openstack-resource-controller/issues/364)

Additions to the Server controller:

• Metadata
• ConfigDrive
• RootVolume
• SchedulerHints

Additions to the Volume controller:

• [x] AvailabilityZone

Additions to the Port controller:

• AdminStateUp
• MACAddress
• Binding Profile
• Binding HostID
• PropagateUplinkStatus
• ValueSpecs

Additional information

The tracking issue in CAPO: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/2814