[several packages] Update jest matcher types

[jgodson]

Description

This PR updates the jest matcher types to be compatible with types in jest 25.

This was updated from the original because it doesn't reflect the merged state.

Original Description:
When working on https://github.com/Shopify/web/pull/22447, I ran into issues when using toHaveReactProps. For some reason it was no longer inferring the typescript types of the React Components. I believe it was due to this change and due to the namespace no longer implementing the same interface it cause these issues.

This PR updates the @types/jest package and the Matcher interface in all packages to match.

Type of change

I'm not sure what type of change this should be. It's a breaking change for Typescript projects, but the update to the types package is the real reason, not these packages themselves

• ast-utilities Minor: jest.Matchers type updated to match @types/jest version 25
• graphql-testing Minor: jest.Matchers type updated to match @types/jest version 25
• react-i18n Minor: jest.Matchers type updated to match @types/jest version 25
• react-testing Minor: jest.Matchers type updated to match @types/jest version 25

Checklist

• I have added a changelog entry, prefixed by the type of change noted above

[GoodForOneFare]

@lemonmade this change makes sense to me. Could you help with Jason's question about what type of version bump this should be in the packages that it touches, please?

[lemonmade]

Sounds good, unfortunately no way to make this a non-breaking change. Since this came as a minor version change on the Jest types, I think I'd do a minor release here and clearly document what Jest type versions coordinate to what package versions in the relevant changelogs.

[vsumner]

Updated to match https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/jest/index.d.ts#L697

[marutypes]

❤️ thanks for looking at this

[alexandcote]

@jgodson, can you check if you have the latest version of @types/jest

I think I already solve this in this PR.

#1295

[jgodson]

Yep your PR fixed React testing, which this originally included as well. This updates the other packages. (I created this PR in January, but took forever to merge it 😅) . Also Victor just commited new changes for another type change in Jest 25 (that's why react-testing is also updated here).

I did forget to update the description though, which I've done now (sorry)

[alexandcote]

My point is Matchers<R> should be valid because T is optional. I think we should only add T if we need it like here.

[jgodson]

Good point, it wasn't optional when I first put the PR up, but it appears that's the changes in jest 25 that Victor added. It shouldn't cause any issues though either in that case? Maybe @vsumner can speak more to those changes as he was the one having issues this time.