fix: adding types to jest matchers

[hanseltime]

Summary

This adds types to describe the FetchMockAdapters and updates the jest Expect object so that typescript and intellisense can provide correct typings. It also adds some typings to the extension.js code so that, if something changes, we'll see that the types fail to compile and we can make updates as needed.

Update - Additional Commit

This commit keeps support for the "patched fetch" and also adds support for FetchMock like the documentation details. It adds tests for both inputs and adds an error message if the input is neither FetchMock or a patched fetch instance.

[wheresrhys]

This is really great - thanks so much for the contribution 🙌

It will also need an update to the docs to explain that fetch can also be used. Are you happy to do that?

[Yihao-G]

As documented here:

filter and options are the same as those used by fetchMock.callHistory.calls().

And calls()'s two arguments are optional:

fetch-mock/packages/fetch-mock/src/CallHistory.ts

Line 79 in b63230f

calls(filter?: CallHistoryFilter, options?: RouteConfig): CallLog[] {

[Yihao-G]

Pretty sure filter and options should be optional here?

[Yihao-G]

Same here

[Yihao-G]

Same here

[hanseltime]

As documented here:

filter and options are the same as those used by fetchMock.callHistory.calls().

And calls()'s two arguments are optional:

fetch-mock/packages/fetch-mock/src/CallHistory.ts

Line 79 in b63230f

calls(filter?: CallHistoryFilter, options?: RouteConfig): CallLog[] {

@Yihao-G - if you think there is an issue with an already merged PR, I would encourage you to open an issue or submit your own PR. People normally don't look at their old merged PRs

[Yihao-G]

I just wanted to double confirm though 😄 - I'm happy to make a PR if you guys think those two parameters should be optional