Catching uncatchables

We were having trouble with spec errors in EventListeners. For example, spec errors thrown when handling the response to an ajax request were uncaught and printed badly.

There are Closure Library functions which can help with these cases. Possibly of use for cljs-devtools

```
(ns condense.preload
(:require [goog.debug.entryPointRegistry :as gepr])
(:import [goog.debug ErrorHandler]))

(defn handle-error [e]
(js/console.debug (.-stack e))
(js/console.debug (ex-data e)))

(def error-handler (doto (ErrorHandler. handle-error)
(.protectWindowSetTimeout)
(.protectWindowSetInterval)
(.protectWindowRequestAnimationFrame)))

(gepr/monitorAll error-handler)
```

Start by tracing how EventListeners handle spec errors from asynchronous Ajax responses, then compare that path with the Closure Library ErrorHandler and entryPointRegistry example in the issue. Done means these errors are caught and reported with useful stack and ex-data output; no source file or test is named, so the relevant integration point must be located first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.