Description of problem:
Multus is supposed to watch for the primary cni config file in /var/run/multus. But it seems to do so only at install time[in essence no watching at all]. If we edit the primary cni config file at /var/run/multus/cni/net.d/10-ovn-kubernetes.conf, it should reflect it in /etc/kubernetes/cni/net.d/00-multus.conf, however it does so only after restarting the multus pods" 

Version-Release number of selected component (if applicable):
Client Version: 4.12.2
Kustomize Version: v4.5.7
Server Version: 4.12.2
Kubernetes Version: v1.25.4+a34b9e9

How reproducible:
Every time

Steps to Reproduce:
1. Edit /var/run/multus/cni/net.d/10-ovn-kubernetes.conf
2. Check /etc/kubernetes/cni/net.d/00-multus.conf


Actual results:
No update to /etc/kubernetes/cni/net.d/00-multus.conf

Expected results:
Updates reflected in /etc/kubernetes/cni/net.d/00-multus.conf

Additional info:
we are editing the file /var/run/multus/10-ovn-kubernetes.conf to chain the cisco cni, but multus does not detect the change

Logs:

2023-06-02T21:13:27+00:00 [cnibincopy] Successfully copied files in /usr/src/multus-cni/rhel8/bin/ to /host/opt/cni/bin/upgrade_18e3dfc8-2f2c-4d88-ac1f-47f2f7df39eb
2023-06-02T21:13:27+00:00 [cnibincopy] Successfully moved files in /host/opt/cni/bin/upgrade_18e3dfc8-2f2c-4d88-ac1f-47f2f7df39eb to /host/opt/cni/bin/
2023-06-02T21:13:27+00:00 WARN: {unknown parameter "-"}
2023-06-02T21:13:27+00:00 Entrypoint skipped copying Multus binary.
2023-06-02T21:13:27+00:00 Generating Multus configuration file using files in /host/var/run/multus/cni/net.d...
2023-06-02T21:13:27+00:00 Using MASTER_PLUGIN: 10-ovn-kubernetes.conf
2023-06-02T21:13:27+00:00 Nested capabilities string: 
2023-06-02T21:13:27+00:00 Using /host/var/run/multus/cni/net.d/10-ovn-kubernetes.conf as a source to generate the Multus configuration
2023-06-02T21:13:27+00:00 Config file created @ /host/etc/cni/net.d/00-multus.conf
2023-06-02T21:13:27+00:00 Entering watch loop...