Fetch 14: Read node extra ca certs, better NO_PROXY logic

[RomneyDa]

trafficstars

Reads certs from NODE_EXTRA_CA_CERTS for custom fetch.

It appears that whenever agent ca is manually set, NODE_EXTRA_CA_CERTS is not read, even though the node docs seem to imply that NODE_EXTRA_CA_CERTS are added to tls on initialization. It seems node-fetch injects these under the hood.

Adds a simple certs cache that caches

• tls and globalAgent certs
• certs read from NODE_EXTRA_CA_CERTS
• caBundlePath successful cert contents

This fixes missing NODE_EXTRA_CA_CERTS and speeds up fetch.

Also adds port and case sensitivity issue fixes for NO_PROXY (taken from https://github.com/continuedev/continue/pull/6115)

[netlify[bot]]

❌ Deploy Preview for continuedev failed. Why did it fail? →

Name	Link
🔨 Latest commit	46f991029d01b94b9a2025a550f66c4d9212970a
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/6851b411b5a65e000824dddf

[recurseml[bot]]

😱 Found 2 issues. Time to roll up your sleeves! 😱

[sestinj]

:tada: This PR is included in version 1.1.0 :tada:

The release is available on:

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

Your semantic-release bot :package::rocket: