Move to new sriovdp

sriovdp release-v1 worked in following way - it scans all VF on the host.
In the current master sriovdp behaves in another way. It uses config (default path /etc/pcidp/config.json).
This config specifies resources to use in sriovdp. For example:
{
    "resourceList":
    [
        {
            "resourceName": "sriov",
            "rootDevices": ["02:00.0", "02:00.1"],
            "sriovMode": true,
            "deviceType": "netdevice"
        },
        {
            "resourceName": "sriov_zero",
            "rootDevices": ["02:00.0"],
            "sriovMode": true,
            "deviceType": "netdevice"
        }
    ]
}

But current kuryr_kubernetes relies on "sriov" resource name concatenated with "intel.com".
We need to extend sriov controller's driver to be able to work with arbitrary resource name.
As we see from config's example, arbitrary resource name is related to pci address (physical device and as a result to physnet). So kuryr-kubernetes should also keep such pair in some mapping attribute in its configuration file.

It's logically to propose physnet_resource_mappings in [sriov] section of the kuryr.conf file.