Use node-fetch instead of request for default transport

[jamierbower]

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[jasonwilliams]

I still get notifications about this 😂

Anyway, looks like a lot of changes, including bumping the minimum version of Node to 18. Any reason you wouldn’t do a 4.0.0 release? This all looks too much to be a patch bump.

The public API may not have changed but there may be unexpected dependencies on requests behaviours (especially after years of use).

As you’re forcing v18 of NodeJS you could use the built in fetch API, but I can understand if you’re put off by the “experimental” tag. My understanding is it’s pretty stable to use and reduces your dependencies.

Just my 2 pence.