Add full WebSocket impersonation

[lwthiker]

Chrome's TLS fingerprint when connecting to a websocket is different than its usual fingerprint (for example, the ALPN tls extension only advertises http/1.1 as a supported protocol). To fully impersonate Chrome on a websocket connection, we need to modify the TLS fingerprint and some HTTP headers.

Currently I'm not aware of any websocket server blocking connections based on fingerprint, so this is on a bit of lower priority.

[mmmray]

+1 on this. currently no ALPN is advertised at all, and CURLOPT_HTTP_VERSION does not help