Execute plugin tests intently in CNAO e2e tests scope

[LakshmiRavichandran1]

What happened:
Hi, we are interested to port CNAO for s390x arch as part of our overall effort to enable Kubevirt on s390x.
You can find some of our initial work here #1916

However, on investigation into to the e2e tests under https://github.com/kubevirt/cluster-network-addons-operator/blob/main/test/e2e/monitoring
we sniffed that the tests triggers once-for-all for different plugins (multus, linux bridge, etc.).

What you expected to happen:
Is there a way to test only specific plugins that we can decide to verify?

How to reproduce it (as minimally and precisely as possible):
Currently, all the different plugins (except multus) are not multi-arch so the e2e tests fails overall for s390x.

Anything else we need to know?:

Environment:

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten