Allow to rename VF in container when using DHCP IPAM and Multus

[Mmduh-483]

By changing the CNI_IFNAME enviroment variable to the VF's new name to
support using intel-multus with renaming interface, when multus move the
interface to the container it will name the first VF eth0 and then
follow the pattern of netX where X start from 0, so when the interface
moved with sriov-cni name mutlus will not find the interface with the
name it set

[zshi-redhat]

This looks like a problem of Multus which doesn't respect the CNI_IFNAME when release/delete the interface. For SRIOV CNI, it receives the pod interface name passing from Multus unless the if0name is set in SRIOV net-attach-def custom resource.