Jest: add Date to setSystemTime param types

[liamfd]

Following up on #45496, this PR adds support for Date arguments to jest.setSystemTime now that jestjs/jest#10169 is merged and released.

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes:
  • https://jestjs.io/docs/en/jest-object#jestsetsystemtime, support for | Date was added in setSystemTime and getRealSystemTime type and doc update jestjs/jest#10169
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
  • (This currently says 16.0, so it's pretty far out of date, but I can make the change if that's desirable)
• Include tests for your changes
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

[typescript-bot]

@liamfd Thank you for submitting this PR!

Code Reviews

Because this is a widely-used package, a DT maintainer will need to review it before it can be merged.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ❌ Most recent commit is approved by DT maintainers

Once every item on this list is checked, I'll ask you for permission to merge and publish the changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 45685,
  "author": "liamfd",
  "owners": [
    "NoHomey",
    "jwbay",
    "asvetliakov",
    "alexjoverm",
    "epicallan",
    "ikatyang",
    "wsmd",
    "JamieMason",
    "douglasduteil",
    "ahnpnl",
    "joshuakgoldberg",
    "UselessPickles",
    "r3nya",
    "hotell",
    "sebald",
    "andys8",
    "antoinebrault",
    "gstamac",
    "ExE-Boss",
    "quassnoi",
    "Belco90",
    "tonyhallett",
    "ycmjason",
    "devanshj",
    "pawfa",
    "regevbr",
    "mskelton"
  ],
  "dangerLevel": "ScopedAndTested",
  "headCommitAbbrOid": "2023b2a",
  "headCommitOid": "2023b2a00aa16f43d7d7f6cd44a33ae47a034cd1",
  "mergeIsRequested": false,
  "stalenessInDays": 0,
  "lastCommitDate": "2020-06-24T12:37:41.000Z",
  "lastCommentDate": "2020-06-24T12:37:41.000Z",
  "reviewLink": "https://github.com/DefinitelyTyped/DefinitelyTyped/pull/45685/files",
  "hasMergeConflict": false,
  "authorIsOwner": false,
  "isFirstContribution": false,
  "popularityLevel": "Critical",
  "anyPackageIsNew": false,
  "packages": [
    "jest"
  ],
  "files": [
    {
      "filePath": "types/jest/index.d.ts",
      "kind": "definition",
      "package": "jest"
    },
    {
      "filePath": "types/jest/jest-tests.ts",
      "kind": "test",
      "package": "jest"
    }
  ],
  "hasDismissedReview": false,
  "ciResult": "pass",
  "lastReviewDate": "2020-06-24T15:20:25.000Z",
  "reviewersWithStaleReviews": [],
  "approvalFlags": 2,
  "isChangesRequested": false
}

[typescript-bot]

🔔 @NoHomey @jwbay @asvetliakov @alexjoverm @epicallan @ikatyang @wsmd @JamieMason @douglasduteil @ahnpnl @JoshuaKGoldberg @UselessPickles @r3nya @Hotell @sebald @andys8 @antoinebrault @gstamac @ExE-Boss @quassnoi @Belco90 @tonyhallett @ycmjason @devanshj @pawfa @regevbr @mskelton - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

[typescript-bot]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#45685	diff
Batch compilation
Memory usage (MiB)	81.2	83.2	+2.4%
Type count	14712	14712	0%
Assignability cache size	4813	4814	0%
Language service
Samples taken	2575	2578	0%
Identifiers in tests	2575	2578	0%
getCompletionsAtPosition
Mean duration (ms)	373.3	370.8	-0.7%
Mean CV	7.9%	8.0%
Worst duration (ms)	497.9	536.0	+7.7%
Worst identifier	calls	afterEach
getQuickInfoAtPosition
Mean duration (ms)	374.2	372.3	-0.5%
Mean CV	8.6%	8.5%	-1.3%
Worst duration (ms)	503.2	488.9	-2.8%
Worst identifier	each	mockResolvedValueOnce

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[mskelton]

Looks good! 👍

[elibarzilay]

@liamfd: I now remember that there was some talk about holding off this change, was it supposed to be merged?

[typescript-bot]

I just published @types/jest@26.0.3 to npm.

[liamfd]

@elibarzilay Hey, sorry, just seeing this.

We pulled it out of #45496 (see #45496 (comment)) because at that time jestjs/jest#10169 hadn't been merged and released, but it has been now, so it seemed safe to add this.

That said, I see that this got released as 26.03, but jest is now at 26.1.0. I think I should have bumped the version number in types/jest/index.d.ts (when I made the PR I thought it was at 16.0, but I now realize that I was looking at types/jest/v16/index.d.ts.) Note that technically, these types are also valid for users of jest 26.0, they will produce code that runs without issue, they just didn't match jest's internal types.

I'm happy to submit a PR to bump the version number in the header if that's beneficial. Sorry, I'm new to contributing to this repo.

[ExE-Boss]

I think the version bump should be done as part of #45603.