fix(testing): let DOM adapter dictate XHR implementation for tests

The test injector now uses an XHR implementation based on DOM.getXHR,
which allows the current DOM adapter to dictate which XHR impl should
be used.

To prevent the changes to DOM adapter from introducing undesired new
dependencies into the benchmarks, separate the async facade into
a promise facade which is reexported by facade/async.

See #4539

modules/angular2/src/testing/test_injector.ts

@@ -115,7 +115,7 @@ function _getAppBindings() {
     PipeResolver,
     provide(ExceptionHandler, {useValue: new ExceptionHandler(DOM)}),
     provide(LocationStrategy, {useClass: MockLocationStrategy}),
-    XHR,
+    provide(XHR, {useClass: DOM.getXHR()}),
     TestComponentBuilder,
     provide(NgZone, {useClass: MockNgZone}),
     provide(AnimationBuilder, {useClass: MockAnimationBuilder}),