Stale field names in libvirt-metal-no-bond.yml

The file common/libvirt-metal-no-bond.yml uses the pre v1.4 field names primary_pool_interface and provisioning_pool_interface under control_plane.capm3 and machine_deployments.md0.capm3. These fields were renamed during the v1.4.0 network schema restructure and are no longer consumed by any Helm template.

Why this hasn't caused a deployment failure

• This file is not actively used: libvirt-metal-no-bond is an option in values_metadatas.yml, meaning it is only applied when a CI job explicitly selects it. No current CI job references this file.
• Helm silently discards unknown value keys at render time: Helm does not error on extra keys during template rendering
• The base values provide valid configuration: e.g The base file capm3-virt-values.yaml already sets:

capm3:
  networks:
    primary:
      interface: bond0.100
    provisioning:
      interface: bond0

The deployment proceeds using the base bond0.100 / bond0 interfaces