WebScale: configure-ovs.sh fails because it picks the wrong default interface

This bug is a backport clone of [Bugzilla Bug 2100181](https://bugzilla.redhat.com/show_bug.cgi?id=2100181). The following is the description of the original bug:
—
Created attachment 1891950
log

Description of problem:

Prior to OCP 4.7.48, the configure-ovs script picked the corrected bonded interface for br-ex. In OCP 4.7.48 we have that is consistently fail. It picks one of the slave interfaces (ens3f0).

Version-Release number of selected component (if applicable):
OCP Release > OCP 4.7.37

How reproducible:
100%

Steps to Reproduce:
1. Deploy an OCP cluster with bonding
2.
3.

Actual results:

Expected results:

configure-ovs should not fail and assign the correct interface to br-ex (bond1)

Additional info:

There appears to be a new default NM profile from 4.7.37 to 4.7.38 a that was not there before