Add support for 'remote-managed' vnic type

The 'remote-managed' vnic type will be used to support off-path
SmartNIC port binding with OVN, and it is expected that the user
will create ports with this vnic type as part of the workflow.

As such the client must allow users to interact with this
vnic type and this patch addresses that.

Partial-Bug: #1932154
Depends-On: I496db96ea40da3bee5b81bcee1edc79e1f46b541
Change-Id: I566c3da594d757dd62edcf7f9ea3077db8d6b11a

Author: fnordahl

openstackclient/network/v2/port.py

@@ -259,11 +259,12 @@ def _add_updatable_args(parser):
         metavar='<vnic-type>',
         choices=(
             'direct', 'direct-physical', 'macvtap',
-            'normal', 'baremetal', 'virtio-forwarder', 'vdpa'
+            'normal', 'baremetal', 'virtio-forwarder', 'vdpa', 'remote-managed'
         ),
         help=_(
             "VNIC type for this port (direct | direct-physical | "
-            "macvtap | normal | baremetal | virtio-forwarder | vdpa, "
+            "macvtap | normal | baremetal | virtio-forwarder | vdpa | "
+            "remote-managed, "
             "default: normal)"
         ),
     )

releasenotes/notes/add-remote-managed-vnic-type-4fc540b47427c37f.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Support for the ``remote-managed`` VNIC type has been added and can now be
+    passed to the ``--vnic-type`` option when used in conjunction with the
+    ``port create`` and ``port set`` commands.