Added fingerprint to websocket connection, in case of upgrading web connection to websocket ( for authentication purposes )

If we authenticate Users via a web connection, the identifier for the session is build with the actionHeroId cookie and so we can check if the user is already authenticated within a page reload.

For example, if there is a websocket connection in the 2nd request of the user, theres no identifier which is matching between the previous web connection and the websocket connection now. But the actionHeroId cookie is provided with the websocket connection upgrade, so we can use the browser fingerprint module twice to detecting the fingerprint for the rawConnection of the websocket.

This resolves the problem that if a web connection is authenticated, a websocket connection from the same client is not authenticated.