Port trusted VIF moved to a Neutron extension

[EmilienM]

/kind bug

In recent Neutron, setting trusted key directly in the port's binding:profile has been deprecated and will be forbidden in future releases.
Dedicated port's attribute trusted, added by the API extension port_trusted_vif should be used instead.

New ML2 plugin extension port_trusted is now available. This extension implements the port_trusted_vif API extension which adds to the port resource a new boolean field called trusted.
This field should be used by admin users to set the port as trusted what was previously possible only through the port's
binding:profile dictionary.

With this extension enabled, it is now possible for admin users to set port as trusted without modifying directly 'binding:profile' field which is supposed to be just for machine to machine communication.

Source: https://review.opendev.org/c/openstack/neutron/+/926068

We need to adapt CAPO with this change bu checking if the extension is enabled.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[EmilienM]

/remove-lifecycle stale