Support top-level onerror for non-DOM guests.

r5701, which introduced a bottleneck function for window.onerror
invocations, did not consider the case of guests without DOM.
Move domicile.handleUncaughtException to be
Domado.handleUncaughtException so that it can be invoked even if
there is no domicile object.

handleUncaughtException now takes the window (or global/imports)
object as an argument, and is not otherwise changed.

Arguably it should be moved out of domado.js entirely, but I
currently think that it makes the most sense there, since onerror
is a browser feature rather than a JS feature, and we do not yet
have a "browser features other than the DOM" module. (One reason
we might gain such is if we provide setTimeout-and-friends in the
no-DOM case, which we probably should.)

@r5703

[felix8a, 2014-10-21 20:36:49]

lgtm. maybe add a TODO somewhere about factoring out non-DOM browser features?

[kpreid_google, 2014-10-21 20:47:50]

On 2014/10/21 20:36:49, felix8a wrote:
> lgtm. maybe add a TODO somewhere about factoring out non-DOM browser features?

I'll file an issue, which I think is more fitting since it's not related to any
given piece of code.

[kpreid_google, 2014-10-21 20:58:07]

On 2014/10/21 20:47:50, kpreid_google wrote:
> I'll file an issue, which I think is more fitting since it's not related to
any
> given piece of code.

https://code.google.com/p/google-caja/issues/detail?id=1857 already existed