find another compatible issue.

• if user use the new version of zone.js
• and they don't set the flag fakeAsyncPatchLock to true, so they don't use auto fakeAsync feature, which is default behavior
• And user still use fakeAsync to work with jasmine.clock().

such as the following sample :

describe('', () => {
  beforeEach(jasmine.clock().install);
  afterEach(jasmine.clock().uninstall);
});

it('user do fakeAsync themselves', fakeAsync(() => {
   // 1. user use jasmine.clock() 
  //  2. and don't use clock patch
  //  3. and user use fakeAsync themselves
 setTimeout(spy, 100);
 expect(spy).not.toHaveBeenCalled();
 jasmine.clock().tick(100);
 expect(spy).toHaveBeenCalled();
}));

This case will fail because jasmine.clock() will also patch setTimeout, so setTimeout will not trigger onScheduleTask. So in this PR, we we make sure if we are in fakeAsync, we will use zone.js patched setTimeout.

So the current behavior of jasmine.clock() is

Conclusion, if testBody is inside of fakeAsync, we will use full package of fakeAsync method instead of jasmine.clock(), if we are not using fakeAsync, we also should make sure jasmine.clock() work as non patched.

other modifications.

• don't patch jasmine.clock() method multiple times.

• can handle jasmine.clock().mockDate() with empty parameters.

• add more test cases.