chore: bump https-proxy-agent to mitigate a security issue

[kachkaev]

Context:

• Man In the Middle vulnerability TooTallNate/proxy-agents#78
• https://app.snyk.io/test/npm/https-proxy-agent/2.2.2
• https://hackerone.com/reports/541502

According to release notes, the bump should not bring any breaking changes for Puppeteer. I believe it can get shipped with the next patch release.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[kachkaev]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[bmeurer]

LGTM, thanks.

[mastermatt]

@mathiasbynens I'm not sure what the release schedule is for this lib, but could we get a patch for this?

[kachkaev]

Also can't wait for a patch release to stop seeing security warnings in Snyk. Some of my projects depend on puppeteer, which brings in vulnerable https-proxy-agent@2.2.2.

🙏

[mastermatt]

@bmeurer and @mathiasbynens it looks like dropping Node v6 support was merged to master since this went in. Will that require a major version bump of puppeteer?
Can I please request that a simple patch version of 1.20 be released with this security vulnerability fixed first?

[warpech]

Fixes #5055