The tests run slow, because afterEach was async but never called done().
because it was afterEach any errors are ignored and so it did not show
up as failure. Instead the test ran very slow until jasmine timed out.

This fix corrects the afterEach and decreases the timeout to 1,000 ms.

When you have in async test (test with `done` argument) jasmine will 
execute the next test synchronously in the done handle. This makes sense
for most tests, but now with zones. With zones running next test 
synchronously means that the current zone does not get cleared. This 
results in a chain of nested zones, which makes it hard to reason about 
it. We override the `clearStack` method which forces jasmine to always 
drain the stack before next test gets executed.

This rewrites the (set/clear)Timeout/Interval/Immediate method to render
information in WTF. It also makes the code more explicit, by removing
the need for bind method and instead creating explicit callbacks. The
resulting code is faster, and easier to read and reason about.

setTimeout/clearTimeout and requeustAnimationFrame/cancelAnimationFrame
have same semantics, so now they share the same code path.

Closes #210

Closes #219

closes #235

On older versions of Chrome, patching via property descriptors isn't
available, but unlike Safari, window.EventTarget exists and is already
patched, so the EventTarget methods on WebSocket.prototype don't need to
be patched again.

Closes #233.