Support Rdma ROCE

[aojea]

Tested using dranet with GKE A3 Mega RDMA nics, see examples/demo_gke_rdma/README.md

The diff is very large because I didn't understand well how RDMA worked and I had several architectural wrong decisions.
The code is also now better organized with a clear differentiation between the operations that need to be done before Pod creating dra_hooks.go and during the pod creation nri_hooks.go. Those files content now a brief comment explaining the expectaction of the code that runs there, specially related to the pod lifecycle.

• RDMA devices are no longer exposed, only network devices, the ones associated to RDMA contain a boolean attribute to indicate it
• RDMA both in shared or exclusive mode move the network and character devices requested to the Pod, in exclusive mode the link RDMA device is also moved to the Pod
• Add a configuration API for definiting Interface attributes and the routes associated to each interface.
• The interface in the host is moved with the existing attributes , addresses and assoicated routes to the interface
• If the interface does not have any address during the prepareResources a best effort to get it via dhcp is done, this is done in the host namespace becuse the external dhcp server only sees the interface, and this is independent of this running in a Pod or the host namespce ... the acquired ip is also not configured until the interface is in the pod namespace
• well known interface names like docker , cilium_host, are now ignored to avoid publishing interfaces that can not be used