reply socks error on more codepath

I think all code-paths in handle_socks_conn now reply something before exiting, except for io errors on the socket, or a few annotated exceptions.

This also close the connection on some happy paths that used to only flush it, but wouldn't reuse it after, relying less on Drop, which is problematic in async context.

fix #258 (closed)