Use wss when creating localhost connection to detect binary support

Some browsers (Firefox) reject unencrypted ws connections if the hosting
page uses https by throwing an exception when you create the websocket
object.

NoVNC interprets this as binary being unsupported, and falls back to
base64.

If we instead connect to wss://localhost, the websocket object can be
created regardless of whether the hosting page is on http or https.
Add support for TightVNC auth type
Removes the connection timeouts to enable slower clients, connections or servers.
Merge pull request #336 from samhed/removeConnectionTimeout

Remove the connection timeouts
Merge pull request #327 from devicenull/master

Add support for connecting to TightVNC servers
Implement XVP auth
Implement XVP extension (shutdown/reboot/reset)
Implement XVP UI in HTML
Merge pull request #242 from Medical-Insight/use-wss-for-binary-detect

Use wss when creating localhost connection to detect binary support (closes #242)
WebSocket protocols are now configurable.
Merge pull request #338 from vatesfr/configurable-ws-protocols

WebSocket protocols are now configurable