Abort the handshake if the client receives a `Sec-WebSocket-Extensions`
header but no extension was requested. Also abort the handshake if the
server indicates an extension not requested by the client.

Refs: #1910

Remove ambiguity and prevent `WebSocketServer.prototype.address()` from
throwing an error if the `noServer` option is used along with the
`port` and/or `server` options.

Ensure that `WebSocketServer.prototype.close()` does not emit a
`'close'` event prematurely if called while the internal HTTP/S server
is closing.

Prevent WebSocket connections from being established after
`WebSocketServer.prototype.close()` is called.

Use the chunk returned by `socket.read()` to handle the buffered data
instead of relying on a `'data'` event emitted after the `'close'`
event.

Refs: nodejs/node#39639

Ensure that `socket.resume()` is called after `socket.pause()`.

Fixes #1940

There is no need to remove the already removed `socketOnData` listener,
resume the socket, and call `websocket.close()` if the socket is already
closed.

If the redirect URL is invalid, then emit the error instead of throwing
it, otherwise there is no way to handle it.

When the value of the `readyState` attribute is `CLOSING`, the internal
socket might still be open. Resume it to read any remaining data and to
allow the connection to be closed cleanly.