Based on my research described in the comment to OSPRH-18547 we should implement support for bond interfaces in `nicMappings` in the way as described below:

I think it can still be something like `map[string]string` and add additional configuration for bonds.

nicMappings:
  - datacentre: eth1
  - ha_dc_network: bond_1

And in such case it would mean that `ha_dc_network` physical network is using bond named `bond_1`.
Now such bond should be configured somehow. I think we can do it as new attribute where bonding name would match device used in the `nicMappings`. So for example above it would be something like:

bondConfiguration:
  - bond_1:
      mode: 'active-backup',
      failOverMac: 1,
      linksInContainer: true,
      miimon: "100",
      mtu: 1500,
      links:
        - name: eth2,
        - name: eth3

and those parameters would be used by the ovn-operator to create bond named `ha_dc_network`. Ovn-operator in such case needs to create:

• NADs for the `eth2` and `eth3` (bond members generally),
• NAD for bond https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/hardware_networks/using-pod-level-bonding#
• Add all of the created NADs to the `ovn-controller-ovs` annotations.