Description of problem:
In recent version, when there is no any port mentioned, nmstate will automatically create an internal port whose name is same with the ovs bridge.
Now this self-created port cannot be easily removed.

Version-Release number of selected component (if applicable):
Verified with:
nmstate-2.2.3-3.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.7-2.el9.x86_64
openvswitch2.15-2.15.0-79.el9fdp.x86_64
DISTRO=RHEL-9.2.0-20230111.33

How reproducible:
100%

Steps to Reproduce:
# step 1
echo "
interfaces:
- name: ovsbr0
  state: up
  type: ovs-bridge
" | nmstatectl apply

# step 2
echo "
interfaces:
- name: ovsbr0
  state: up
  type: ovs-bridge
  bridge:
    port:
    - name: ovs0
" | nmstatectl apply

Actual results:
[2023-01-13T09:14:40Z INFO  nmstate::iface] Include interface ovsbr0 to edit as its controller required so
[2023-01-13T09:14:40Z INFO  nmstate::iface] Interface ovsbr0 cannot live without controller, marking as absent as it has been detached from its original controller ovsbr0
[2023-01-13T09:14:40Z INFO  nmstate::ifaces::inter_ifaces_controller] Creating new OVS internal interface ovs0 to edit as its controller ovsbr0 required so
NmstateError: InvalidArgument: Interface ovs0 cannot be in up state as its parent ovsbr0 has been marked as absent

Expected results:
No failure
Internal port(type: ovs-interface) ovsbr0 is removed, internal port ovs0 is created

Additional info:
Explicitly marking it as absent doesn't work neither:
interfaces:
- name: ovsbr0
  state: up
  type: ovs-bridge
  bridge:
    port:
    - name: ovs0
- name: ovsbr0
  state: absent
  type: ovs-interface
- name: ovs0
  state: up
  type: ovs-interface


But in step 2, if adding a *system* interface without any internal interface, it can work:
interfaces:
- name: ovsbr0
  state: up
  type: ovs-bridge
  bridge:
    port:
    - name: veth0 # a system interface