Moved setting isReloading flag and logging closer to where the actual reload is done.
Clarified why isReloading is set to true while disconnecting.

The circular dependency of functions connect -> onClose -> reconnect is valid, so added 'reconnect' as a global to the jslint config to make it happy.

CMS7-8406: use console.log instead of console.debug, and check whether console.log is available before logging

IE10 does not support console.debug, while console.log is supported in all recent browsers.

CMS7-8404: use 'beforeunload' instead of 'unload' event to close websocket connection before page reload

CMS7-8367 remove prefix exclusion as bootstrapped too late which is not allowed. Hardcode separate /autoreload skip in hst

The websocket will always be closed in the disconnect() function on page unload

The service provided a JavaScript snippet that lets a browser connect to the auto-reload server using WebSockets. Whenever #broadcastPageReload is called, a 'reloadPage' message is sent to all connected browsers that will then reload the current page. 

When a WebSocket connection is closed unexpectedly (e.g. because the server is stopped), the JavaScript snippet tries to reconnect every five seconds for 10 minutes, and then gives up.

The auto-reload service is enabled by default. It can be toggled via the configuration parameter 'enabled'. Changes to the JCR configuration are picked up and effective immediately. The auto-reload service can also be disabled via code using the #setEnabled method.

The auto-reload service is supposed to be injected into Tomcat's shared/lib folder by Cargo, so it'll only be available during local development. For that reason only dependencies can be used that are available in the shared/lib folder. The WebSockets API implementation is provided by Tomcat.