Switch request to node-fetch and update dependencies

[strmer15]

The current implemenation of taxjar-node uses request under the hood, but the library has been deprecated for two years now. This change switches out usage of request and request-promise-native for the node-fetch library.

The main differences in the implementation are:

• The URL is constructed ahead of time and passed as the first parameter to fetch. This means that the base apiUrl, the path to the API endpoint, and the query params are all constructed using the URL and URLSearchParams constructors. Those APIs are only available in Node 10+, so this updates the minimum supported version of Node to 10.
• When a status code error occurs, an exception is not thrown automatically. In this implementation, I'm checking for response.ok, which is a convience property to check for a status code >= 200 and < 300.. When that is not set, I'm attempting to get the response body and parse into JSON for the proxyError function to deal with. This should be functionally equivalent to what happens currently with request-promise-native (see the Promise core plumbing at https://github.com/request/promise-core/blob/master/lib/plumbing.js#L68 and the error declarations in https://github.com/request/promise-core/blob/master/lib/errors.js).

Additionally, I updated some types to use Record<string, string> which is what the URLSearchParams expects for query params, and I updated all the dev dependencies to the latest. The newest version of nock specifically checks for invalid URLs (e.g. without a protocol) and throws an error, so I put an http:// in front of the test invalidApiUrl. Lastly, the include check on one of the tests failed because the error message was longer but included the error string, so I changed to to call match on the err.message using a RegExp instead.

[CLAassistant]

All committers have signed the CLA.

[strmer15]

@fastdivision @sethobey Not sure who can review this, can you point me in the right direction? Thanks!

[meecect]

There is a new advisory that affects the product now as well:

GHSA-p8p7-x288-28g6

[neverbot]

I created an issue (#76), just in case... maybe somebody sees it :)

[akv-mshin]

Also sent e-mail to taxjar support, hope that this will increase chances of this PR being merged

[smolentzov-stripe]

Hi @strmer15 - thank you so much for submitting this PR, and for the thorough description. We have reviewed it and are planning on merging/releasing it early next week! We really appreciate everyone's patience here.

[strmer15]

Thanks for the update @smolentzov-stripe !