feat: prefer global fetch on Node.js

[ChALkeR]

Native fetch is no longer behind the experimental flag since Node.js 18.0.0, and is marked stable since Node.js 21.0.0
And the current impl in v20.11+ is newer then the one in v21.0.0

This leaves the backwards-compat in place with environments with no global fetch, and only prefers it over node-fetch

We can remove node-fetch fallback in v2 or v1 as we don't really need it anymore and all supported Node.js versions have global fetch

[mvayngrib]

utACK

this seems like a potentially breaking change, no? Or does node-fetch also use global fetch underneath if it's available?

[ChALkeR]

@mvayngrib

this seems like a potentially breaking change, no?

It is, technically

Or does node-fetch also use global fetch underneath if it's available

No

Clients should expect to be compatible with browser/global fetch already though, as they are used in different envs
So I wouldn't count this as a major breaking change, just as a semver-minor, to not cause extra update churn

Also, this can be overriden in specific setups

[github-actions]

🎉 This PR is included in version 1.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀