fix: remove jest interface types as they can be imported from jest itself

[SimenB]

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: ☂️TypeScript migration tracking issue jestjs/jest#7807
• 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.
• 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.

Since Jest has been rewritten to TypeScript, all of these interface types can be imported directly from Jest's individual modules. The major of Jest 25 is the perfect time to remove these 🙂

[SimenB]

I added this in #33030 due to a bug in the publisher meaning it wasn't added as a dependency. However, it was not removed when @types/jest-diff was deprecated in #39589.

[typescript-bot]

@SimenB Thank you for submitting this PR!

🔔 @NoHomey @jwbay @asvetliakov @alexjoverm @epicallan @ikatyang @wsmd @JamieMason @douglasduteil @ahnpnl @JoshuaKGoldberg @UselessPickles @r3nya @Hotell @sebald @andys8 @antoinebrault @favna @gstamac @ExE-Boss @quassnoi @Belco90 @tonyhallett @ycmjason @devanshj - 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.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

[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?

These typings are for a package that doesn’t yet exist on master, so I don’t have anything to compare against yet! In the future, I’ll be able to compare PRs to jest with its source on master.

Comparison details 📊

Batch compilation
Type count	14514
Assignability cache size	35860
Language service measurements
Samples taken	2541
Identifiers in tests	2541
getCompletionsAtPosition
Mean duration (ms)	358.8
Mean CV	8.8%
Worst duration (ms)	481.9
Worst identifier	jest
getQuickInfoAtPosition
Mean duration (ms)	356.5
Mean CV	9.1%
Worst duration (ms)	466.8
Worst identifier	b
System information
Node version	v12.14.1
CPU count	2
CPU speed	2.294 GHz
CPU model	Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
CPU Architecture	x64
Memory	6.8 GiB
Platform	linux
Release	4.15.0-1066-azure

[typescript-bot]

A definition owner has approved this PR ⭐️. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution to DefinitelyTyped!

[typescript-bot]

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