When unexpected response sent by server, make the request and response available.
Fixes these problems:
(a) The request and response hang around (preventing process exit) until timeout
    - call err.request.abort to stop this
(b) It's very useful to be able to read the response! There may be extra error
    information returned by the server that can't be represented by the status
    code alone (e.g. some JSON data describing the error).
NodeV4 pass agent
New event, for unexpected response ('unexpected-response').
If there's a handler, it's expected to take care of reading and closing it.
Otherwise, the request/response is closed and 'error' is emitted.
When unexpected response sent by server, make the request and response available.
Fixes these problems:
(a) The request and response hang around (preventing process exit) until timeout
    - call err.request.abort to stop this
(b) It's very useful to be able to read the response! There may be extra error
    information returned by the server that can't be represented by the status
    code alone (e.g. some JSON data describing the error).
NodeV4 pass agent
New event, for unexpected response ('unexpected-response').
If there's a handler, it's expected to take care of reading and closing it.
Otherwise, the request/response is closed and 'error' is emitted.
Put back blank lines
Merge branch 'master' of github.com:davedoesdev/ws

Conflicts:
	lib/WebSocket.js
Merge pull request #271 from davedoesdev/master

When unexpected response sent by server, make the request and response available