fix: upgrade to node-fetch@3.X MONGOSH-1702

[paula-stacho]

https://jira.mongodb.org/browse/MONGOSH-1702

Description

The new version doesn't work with our tsconfig, that's why the "skipLibCheck". I hope it's okay I added it to the common config, I've seen we already have it in @mongodb-js/tsconfig-devtools

Code changes are due to:

1. response.body can be null - this was probably already true before, just the types were weaker. the upgrade guide only mentions removing a string option. from what I see we've been treating it as a stream. https://github.com/node-fetch/node-fetch/blob/main/docs/v3-UPGRADE-GUIDE.md#reqbody-can-no-longer-be-a-string
2. response.json() is Promise<unknown>. again, the types were probably just weaker before and it passed as any.
3. node-fetch is now an ES module https://github.com/node-fetch/node-fetch/blob/main/docs/v3-UPGRADE-GUIDE.md#converted-to-es-module -> this one created considerable issues in different builds and per @addaleax's suggestion led to the creation of the import-node-fetch wrapper
4. once is now recommended when listening for errors https://github.com/node-fetch/node-fetch/blob/main/docs/v3-UPGRADE-GUIDE.md#a-stream-pipeline-is-now-used-to-forward-errors

Note: You'll see the code updates in the build package as well, but not the version change. Originally I thought I might as well upgrade node-fetch everywhere, but the ES Module doesn't work with ts-node. Looks like ESM support in ts-node comes with a warning, and this isn't directly connected to the deprecation warning in homebrew, so I think we can leave this on 2.x for now.