chore(deps): upgrade http/https/socks proxy agents

[TheBoroer]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

This fixes a bug where a monitor using a HTTPS proxy server which is configured with a cert that uses a newer root cert (e.g. LetsEncrypt) would throw an error saying self-signed certificate but it's actually valid. Checking the https proxy manually in any browser works + using any ssl checker tool also verifies that the cert is valid. Currently the only way to get the http check to pass is to enable the Ignore TLS/SSL error for HTTPS websites checkbox.

Upgrading the https-proxy-agent package fixes this issue. Since the HttpsProxyAgent syntax changed slightly (requiring a proxy url string instead of proxyOptions to be fed in), I've also gone ahead and upgraded http-proxy-agent and socks-proxy-agent so that all proxy options use the same syntax now.

I can provide a test https proxy that causes monitor checks to fail on the latest version of uptime-kuma but works with this fix, just lmk and I'll get you a temp user/pass combo for this PR.

Type of change

Please delete any options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

[CommanderStorm]

I can provide a test https proxy that causes monitor checks to fail on the latest version of uptime-kuma but works with this fix, just lmk and I'll get you a temp user/pass combo for this PR.

Either this or the pinky-promise that you have tested both proxys still work:

• http and
• sock

I'd like to pull this to v2 as a "feature".

[TheBoroer]

Either this or the pinky-promise that you have tested both proxys still work:

• http and
• sock

I'd like to pull this to v2 as a "feature".

I'll take the pinky-promise (and here's my proof 🫡 🤝 )

[CommanderStorm]

I have changed the base to be v2.
There are now a two merge conflicts, could you fix them? ^^

[CommanderStorm]

LGTM