fix: remove global override of fetch

[andrew-scott-fischer]

Feel free to help me get tests passing!

Ticket: #1193

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• Commit messages follow the conventional commits spec
• If this is a code change: I have written unit tests.
• If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Attempting to use the node native fetch API in node >= 18 when the near-api-js is imported directly or by a transitive dependency results in the node global fetch property being overwritten by near-api-js.

These two lines of code here and here explicitly override the global fetch property.

They should not do this.

Test Plan

I am not sure how to test this. Suggestions welcome

Related issues/PRs

#1193

[changeset-bot]

🦋 Changeset detected

Latest commit: 89667fc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
near-api-js	Patch
@near-js/providers	Patch
@near-js/cookbook	Patch
@near-js/accounts	Patch
@near-js/wallet-account	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[frol]

This change makes total sense, thanks for addressing this cruel manipulation with the global object.

[andrew-scott-fischer]

@frol I see the last release was ~5 months ago; any idea when the next one will be?

[frol]

@andrew-scott-fischer I don't feel adventurous to do it before NEARCON, and then one week after NEARCON will be also a catch up game, so I would hope that we can have a release in the second half of November.