if the bind shell example is compiled with the right feature and is run
inside a(n) (im)properly configured Docker container, it is now able to
break out and run some commands on the host
for some reason, under this breakout mode, it runs a little weird with
networking commands, but does fine with file system or IPC based commands
Made it use a single UDP client as well as proper randomized ports to go
through network firewalls, requiring stdin, status, stderr, and stdout
all go over a single UDP socket
Updated the client to have a prompt
