build: upgrade zone.js

[JiaLiPassion]

based on #23100
Upgrade zone.js to latest version, currently this PR is just for test, because it depends on my zone.js branch.
in zone.js 0.8.21, there are several feature which break angular test.

1. move async/fakeAsync from angular to zone.js
2. support jasmine.clock() to be auto jump into fakeAsync

beforeEach(() => {
      jasmine.clock().install();
    });

    afterEach(() => {
      jasmine.clock().uninstall();
    });

    it('should get date diff correctly', () => {  // we don't need fakeAsync here.
      // automatically run into fake async zone, because jasmine.clock() is installed.
      const start = Date.now();
      jasmine.clock().tick(100);
      const end = Date.now();
      expect(end - start).toBe(100);
    });

this feature break the test cases in aio. https://github.com/angular/angular/blob/master/aio/src/app/app.component.spec.ts#L1110
which use jasmine.clock() to simulate timer, but still use async/await, so it will be TIMEOUT, in this PR, just remove async/await and use tick.

3. several test cases in angular will be timeout, https://travis-ci.org/angular/angular/jobs/360448001
   the reason is because zone.js AsyncTestZoneSpec add a new feature to be able to wait non resolved promise.then, it seems this feature will have a big impact to current angular test cases, for example, in the following case,
   https://github.com/angular/angular/blob/master/packages/compiler/test/metadata_resolver_spec.ts#L87
   current test case seems have some error, that the promise.then never invoked, but in earlier version of zone.js, this test case will pass, but in zone.js 0.8.21, this will fail. there are several similar cases, so I just disable this feature in fix(fakeAsync): fix #1050, should only reset patched Date.now until fakeAsync exit  zone.js#1051, and I will check all related test cases in angular later.

[mhevery]

There seem to be a lot of unrelated formatting changes in the source code. Could you revert those?

Thank you for looking into this.

[mhevery]

should this file be reverted?

[JiaLiPassion]

@mhevery , yes, I will revert it now.

[IgorMinar]

Is this a breaking change in zone.js that should be documented and require a minor version bump?

In other words do we expect others to have to make these changes as well? Should we update our testing docs?

[JiaLiPassion]

@IgorMinar , I will update the test document now, about the break change such as user don't need to write fakeAsync when using jasmine.clock, I am not sure where I should document it. should it be documented in change log?

[mhevery]

http://test/OCL:191203213:BASE:191205328:1522554599721:35b889b4

[gkalpak]

Shouldn't this be replaced to point to an npm release?

[JiaLiPassion]

@gkalpak , sure, if the g3 test passed, zone.js will have a new release

[gkalpak]

Shouldn't this be replaced to point to an npm release?

[JiaLiPassion]

same as above.

[gkalpak]

Removed the merge label because of #23108 (comment).
@mhevery, feel free to add it back if it was intentional to use @JiaLiPassion's branch.

[mhevery]

http://test/OCL:191203213:BASE:191454769:1522774185137:e300ca42

[ngbot]

Hi @JiaLiPassion! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

resolved

[gkalpak]

🎉

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}