macvtap.network.kubevirt.io/ do not get removed when uninstalling macvtap

[tstirmllnl]

What happened:
It also looks like macvtap.network.kubevirt.io/ resources from previous runs stay behind and don't get cleared when you remove the macvtap.

Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource                                  Requests    Limits
  --------                                  --------    ------
  cpu                                       702m (1%)   770m (1%)
  memory                                    815Mi (0%)  320Mi (0%)
  ephemeral-storage                         0 (0%)      0 (0%)
  hugepages-1Gi                             0 (0%)      0 (0%)
  hugepages-2Mi                             0 (0%)      0 (0%)
  devices.kubevirt.io/kvm                   0           0
  macvtap.network.kubevirt.io/dataplane      0           0
  macvtap.network.kubevirt.io/dataplanea     0           0
  macvtap.network.kubevirt.io/dataplaneab    0           0

What you expected to happen:
macvtap.network.kubevirt.io/ to not show up when running kubectl describe on a node.

How to reproduce it (as minimally and precisely as possible):

1. Install macvtap.
2. Run kubectl describe node <node> to see list of macvtap.network.kubevirt.io/ resources
3. Remove macvtap from cluster
4. Run kubectl describe node <node> and you will see a list of macvtap.network.kubevirt.io/ resources.

Additional context:
Add any other context about the problem here.

Environment:

• KubeVirt version (use virtctl version): 1.1.0
• Kubernetes version (use kubectl version): 1.23.9
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: Baremetal
• OS (e.g. from /etc/os-release): CentOS 7
• Kernel (e.g. uname -a): 3.10.0-1160.11.1.el7.x86_64
• Other Tools: Multus Thick client(4.0.2)

[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