Secure WebSocket connection on authentication with Http cookies

[Aschen]

Feature Description

When using the WebSocket protocol with the SDK, the login action will be sent through HTTP with the secured way described below.

Once the cookie is set in the browser, the SDK can start the WebSocket handshake (which is through HTTP so the cookie will be sent) so Kuzzle have to handle the cookie sent during this handshake to authenticate the connection for the duration of the token.
The token is not needed in the subsequent request since Kuzzle already authenticate the websocket connection.

⚠️ This is not enough to protect WebSocket against CSRF https://christian-schneider.net/CrossSiteWebSocketHijacking.html

See also:

• Use HttpOnly cookies to authenticate the SDK in the browser with HTTP kuzzle#1884
• Secure authentication renewal with WebSocket connection #592