Remove assertions and properly handle send/recv errors

The TGen plugin has several send/recv assertions when setting up a SOCKS connection. It is possible that the socket closed or has some other error, even during the setup phase, and these assertions would cause the program to abort in this case. We should properly handle the return vals from send/recv instead of asserting that the amount we tried to send/recv actually got sent/recved.
