zone.js support jest test.each() methods, but it
introduces a bug, which is the done() function will not be handled correctly.

it('should work with done', done => {
  // done will be undefined.
});

The reason is the logic of monkey patching test method is different from jasmine patch

// jasmine patch

return testBody.length === 0
   ? () => testProxyZone.run(testBody, null)
   : done => testProxyZone.run(testBody, null, [done]);

// jest patch

 return function(...args) {
   return testProxyZone.run(testBody, null, args);
 };

the purpose of this change is to handle the following cases.

test.each([1, 2])('test.each', (arg1, arg2) => {
  expect(arg1).toBe(1);
  expect(arg2).toBe(2);
});

so in jest, it is a little complex, because the testBody's parameter may be bigger than 1, so the
logic in jasmine

return testBody.length === 0
   ? () => testProxyZone.run(testBody, null)
   : done => testProxyZone.run(testBody, null, [done]);

will not work for test.each in jest.

So in this PR, I created a dynamic Function to return the correct length of paramters (which is required by jest core), to handle

1. normal test with or without done.
2. each with parameters with or without done.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: The issue is found at jest-preset-angular repo here, thymikee/jest-preset-angular#356