Containerized: Distribute kuryr-driver as virtualenv, not pyinstaller binary

Currently, in containerized deployments, kuryr-driver (the part K8s CNI calls) is injected onto the host system as pyinstaller binary with all the dependencies included. While this seemed to be a good idea it has several disadvantages:

* Build process takes longer time and requires spawning 2 containers.
* There are meaningless errors in kubelet logs that are caused by the fact we're using pyinstaller binary instead of script interpreted by Python.

To work around that this blueprint plans to base kuryr-driver injection on virtualenv that gets copied onto the host system.