Add OVS access support for ethernet interfaces

[wasnio]

Add support for the ovs_access parameter on ethernet interfaces in the Deployment Manager. This enables configuring OVS access on an ethernet interface that sits on top of a pci-sriov lower interface, allowing OVS to use the physical function as an uplink port.

Add the ovsAccess field to the EthernetInfo CRD type and update the reconciler to pass ovs_access when creating or updating ethernet interfaces via the sysinv API. Add a new ethernetUpdateRequired function to detect changes to the ovs_access attribute.

Add webhook validation enforcing the following constraints:

• ovsAccess requires a lower interface of class pci-sriov
• The lower pci-sriov must not have platform networks assigned
• Only one ethernet interface per host can have ovsAccess enabled
• VLAN interfaces cannot be added on the same pci-sriov lower
• Bond interfaces cannot use the same pci-sriov as a member

Update the gophercloud Interface and InterfaceOpts structs to include the ovs_access field. Update constructors to capture ovs_access from the running system for deployctl and host defaults collection.

Test Plan:

PASS: Deploy AIO-SX system with ovsAccess=true on an ethernet
      interface over a pci-sriov lower. Verify system host-if-show
      reports ovs_access=True on the interface.
PASS: Webhook correctly rejects invalid configurations (no lower,
      lower not pci-sriov, lower has platform networks, multiple
      ovsAccess interfaces).
PASS: Day-2 setting ovsAccess=false on an ethernet
      interface over a configured pci-sriov lower. Verify system
      host-if-show reports ovs_access=False on the interface.