driver: drop NBD implementation (moved to libwnbd)

Now that the nbd client implementation has been moved to libwnbd,
we can drop it from the driver.

We're keeping the WNBD_PROPERTIES structure mostly the same for
backwards compatibility reasons, except for a small change:
we're adding a separate flag to advertise the userspace nbd client
in order to avoid incorrect behavior with older driver versions
(e.g. having both libwnbd and the driver attempt to initiate
NBD connections).

The WNBD tests and CLI client are updated to use the libwnbd NBD
client implementation. One thing to note here is that the
"wnbd-client map" now becomes a blocking command, running the
daemon in background.

Signed-off-by: Lucian Petrut <[email protected]>

Author: petrutlucian94

README.md

@@ -52,7 +52,6 @@ Folders
 * [Dockerfile](Dockerfile/) a Dockerfile providing the build prerequisites
 * [driver](driver/) the driver sources
 * [include](include/) public headers
-* [ksocket_wsk](ksocket_wsk/) a WSK wrapper used to communicate with the Network Block Device server
 * [wnbd-client](wnbd-client/) the WNBD CLI
 * [libwnbd](libwbd/) ``libwnbd.dll`` - the WNBD userspace library
 * [vstudio](vstudio/) the Visual Studio solution file and its projects