fix: respect rejectUnauthorized and ca opts when proxying https

[cwilper]

This PR fixes #362

Problem

When Bruno would make SSL/TLS connections through a proxy, it would not respect connection options like rejectUnauthorized or ca. This was making it difficult to use when going through a self-signing MiTM proxy, or using a custom certificate authority.

Cause

The issue was caused by an upstream bug in https-proxy-agent, where it doesn't permit options to be passed down when upgrading sockets to TLS:

• connectOpts are ignored when upgrading socket connection to TLS TooTallNate/proxy-agents#194

The same underlying issue has been reported against multiple versions of that library over the years. As you can see in the comments, people have either switched to other libraries, or patched it to pass down such options:

• Doesn't seem to pass options to tls.connect TooTallNate/proxy-agents#89
• Http-proxy-agent with Axios library, Https agent properties does not work TooTallNate/proxy-agents#121

Solution

The solution employed here is to patch the class, similar to what others have done.

When/if the issue is fixed in proxy-agents, that should be used instead.

Note to Reviewers:

• I put this in the existing proxy-util.js file, which is currently duplicated for CLI and Electron. I didn't see a good way to just have one copy of the code. Maybe the JS package would make sense eventually -- there seems to be lots of opportunity for consolidating common code there.
• I was able to test successfully using the UI, but not the CLI -- I think there may be a separate bug in CLI currently where the Collection-configured proxy is not actually attempted to be used -- the code seems to look for proxy.enabled: true but it's saved as proxy.use: true in my bruno.json file in the collection dir. I didn't try to address that as part of the PR, as it seems a separate topic.

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have read the contribution guidelines.
• Linked issue to the pull request.

[helloanoop]

@cwilper You're awesome !!!

there seems to be lots of opportunity for consolidating common code there.

Yup, post out v1 launch, we will consolidate this.

I was able to test successfully using the UI, but not the CLI -- I think there may be a separate bug in CLI currently where the Collection-configured proxy is not actually attempted to be used -- the code seems to look for proxy.enabled: true

Yup, this discrepancy needs to be fixed. We will be using enabled in both places.

Thanks again @cwilper !

Merged!