fix(http-connect): try wrapping fetch so that it's passed and agent t…

[MarcMcIntosh]

https://linear.app/prismic/issue/DT-1271/pushing-changes-sometimes-fails-with-error-getaddrinfo-enotfound

Looks like enotfound errors could be coming from node-fetch
node-fetch/node-fetch#449
and
node-fetch/node-fetch#79
seems that lots of requests, looks like people are fixing it by passing a user agent node-fetch/node-fetch#1735

Context

The Solution

Impact / Dependencies

Checklist before requesting a review

• I hereby declare my code ready for review.
• If it is a critical feature, I have added tests.
• The CI is successful.
• If there could backward compatibility issues, it has been discussed and planned.

[OPT] Preview

[bapmrl]

⚠️ This fix might work, but it would be reassuring if we could find a way to reproduce the issue 🙂

Also, I think the manager's tests should be using the same packages/manager/src/lib/fetch.ts module for consistency.

Note that I found more explanations here: node-fetch/node-fetch#1735.

[angeloashmore]

Inline with @bapmrl's comment, it would be good to have a reproduction of the issue or a test that confirms this fix is effective. However, I understand that would be tricky to implement.

The implementation could be simplified, in my opinion, as well as benefit from some context around why the wrapper exists.

I opened a PR with some changes (it was quicker to write the changes than to explain them): #961

Feel free to use it or not. 🙂