This story's goal is to support network policies for ovn-k when the IP address of the pod interface was not configured by OVN.

Virt users would - for instance - apply that via cloud-init / some external DHCP server / setting a static IP address.

For pods, I would say the same applies - except cloud-init.

Users of multi-net policy for networks without OVN-K controlled IPAM will only be able to express policies using `ipBlock` - podSelectors and namespaceSelectors would not be possible.

Definition of done:

• code merged upstream
• e2e tests
• upstream documentation updated w/ the limitations