We weren't destroying our references to `iframe`s after removing those
frames from the DOM, so we would slowly accumulate more and more
frames as time went on.

Partially addresses #724

Closes #753

Closes #742

Closes #740

Fix a couple of strong mode runtime cast errors.

In strong mode, a generic type instantiated with dynamic is not a
subtype of all types. You can't pass a List<dynamic> to something
expecting, say, List<int>.

These errors are usually detected statically, and most of those have
been fixed. However, sometimes this becomes a runtime cast, as in:

main() {
  // Store a List<dynamic> in a variable of type dynamic.
  dynamic d = [];

  // Implicit runtime downcast from dynamic to List<String>.
  List<String> s = d;
}

In order to ease the migration to strong mode, DDC has been ignoring
these cast failures when they involve certain commonly used types. We
are now in the process of actively fixing those errors.

More context: https://github.com/dart-lang/sdk/issues/27223

We were previously communicating over standard in/out, but this was
fragile: if raw JS code printed anything to stdout, it would break our
connection.

Closes #726

Closes #417

addTearDown() now adds a tearDownAll() rather than adding a plain
tearDown() when called from within setUpAll() (or tearDownAll()). This
is technically a behavioral change, but the old behavior was so
useless I doubt anyone was relying on it.

Closes #712

Use Stdout.terminalColumns for line length

Fall back on a 200-character default, which is less likely to obscure
test names when printing to a non-terminal destination.

Closes #86 

This makes it possible to use the same spawnHybridUri() call from
multiple test files that are in different places in the filesystem.

See #391

Closes #688

* Adapt for strong-mode changes to zone.

* Use `runGuarded` instead of `runUnaryGuarded`.

* Increment version number.

* Add Changelog entry.

* Drain and ignore

* add changelog and pubspec

* extend timeout

This also makes CompilerPool more general, so it can be used by both
the node and the browser platforms.

Run tear-downs in the same error zone as tests.

We used to create a new error zone for each call to
waitForOutstandingCallbacks(), which meant that asynchronous errors
couldn't be safely passed around within a single test. Now we have a
single error handler that manually checks the zone in which the error
was thrown.

Closes #621