Description of problem:
Currently nmstate doesn't suepport reating an OVS bridge, with a VLAN port in trunk mode and trunk-tags range.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux CoreOS 411.86.202207150124-0
RHEL 8.6
NetworkManager (on cluster worker node): 1.36.0-7.el8_6
NetworkManager (on nmstate-handler pod): 1.36.0-7.el8_6
nmstate (on nmstate-handler pod): nmstate-1.2.1-3.el8_6.x86_64


How reproducible:
100%


Steps to Reproduce:
1. Create an OVS bridge with a VLAN port in trunk mode and trunk-tags range.
I used the following policy to achieve that:

apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: ovs-bridge-policy
spec:
  desiredState:
    interfaces:
    - bridge:
        options:
          stp: false
        port:
        - name: eno4
          vlan:
            mode: trunk
            trunk-tags:
            - id-range:
                max: 1019
                min: 1000
      name: br1test
      state: up
      type: ovs-bridge
  nodeSelector:
    node-role.kubernetes.io/worker: ""

(Modify port name and VLAN id-range per according to your environment).


Actual results:
The configuration fails to configure after timeout:
$ oc get nncp -w
NAME                STATUS        REASON
ovs-bridge-policy   Progressing   ConfigurationProgressing
ovs-bridge-policy   Progressing   ConfigurationProgressing
ovs-bridge-policy   Degraded      FailedToConfigure


Expected results:
Successful configuration.


Additional info:
1. This configuration is not supported in NetworkManager as well (not only in nmstate).

2. The same configuration succeeds when the bridge type is linux-bridge, i.e.
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: linux-bridge-policy
spec:
  desiredState:
    interfaces:
    - bridge:
        options:
          stp: false
        port:
        - name: eno4
          vlan:
            mode: trunk
            trunk-tags:
            - id-range:
                max: 1019
                min: 1000
      name: br1test
      state: up
      type: linux-bridge
  nodeSelector:
    node-role.kubernetes.io/worker: ""

3. The same configuration (OVS bridge) succeeds, with a VLAN port in access mode and an explicit ID tag, i.e.
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: ovs-bridge-policy
spec:
  desiredState:
    interfaces:
    - bridge:
        options:
          stp: false
        port:
        - name: eno4
          vlan:
            mode: access
            tag: 1021
      name: br1test
      state: up
      type: ovs-bridge
  nodeSelector:
    node-role.kubernetes.io/worker: ""

4. This was found on RHEL 8.6, however it can be targeted to RHEL 9.