fix: change dependency override

[oliveriosousa]

• Change node-fetch dependency resolution

This change is needed to run the examples in the web sandboxes (like codesandbox and stackblitz)

When testing the examples using the stackblitz it throws an error:

Unable to resolve package (node-fetch npm:@achingbrain/node-fetch@^2.6.4) Please try installing a different version or range.

CC: @achingbrain @hugomrdias

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[lidel]

This is blocked until Node v16 becomes LTS (~2021-10-26 according https://nodejs.org/en/about/releases/).
We need the fork until then.

[hugomrdias]

This is blocked until Node v16 becomes LTS (~2021-10-26 according https://nodejs.org/en/about/releases/).
We need the fork until then.

@lidel can you explain why ? if achingbrain/native-fetch#3 gets merged it should be ok

[achingbrain]

Why was this necessary?

[oliveriosousa]

At the moment of the PR, the CI was failing due to some types.

> aegir build --no-bundle

[11:21:13] Clean ./dist [started]
[11:21:13] Clean ./dist [completed]
[11:21:13] Generate types [started]
src/http.js(140,7): error TS2345: Argument of type 'AbortController | AbortController' is not assignable to parameter of type 'AbortController'.
  Type 'import("/home/runner/work/js-ipfs-utils/js-ipfs-utils/node_modules/abort-controller/dist/abort-controller").default' is not assignable to type 'AbortController'.
    Types of property 'signal' are incompatible.
      Property 'abort' is missing in type 'import("/home/runner/work/js-ipfs-utils/js-ipfs-utils/node_modules/abort-controller/dist/abort-controller").AbortSignal' but required in type 'AbortSignal'.
[11:21:16] Generate types [failed]
[11:21:16] → Command failed with exit code 1: tsc --build /home/runner/work/js-ipfs-utils/js-ipfs-utils/tsconfig-types.aegir.json
Command failed with exit code 1: tsc --build /home/runner/work/js-ipfs-utils/js-ipfs-utils/tsconfig-types.aegir.json

This was a quick and dirty solution to fix in order to test in codesandbox but without success. I was targeting this PR instead and the sandbox did not like it either.

[lgaroche]

Note that this change breaks environments where the npmjs registry is not available (such as corporate proxied networks). Even if a custom registry is configured, npm will try to download the dependency from npmjs.