🐛 Same as #350 but No one seems to get the answer. HTTP_PROXY and HTTPS_PROXY isn't respected for tunnel commands

**Describe the bug**
Even after setting the http_proxy and https_proxy the tunnel command doesn't respect it.
**To Reproduce**
Steps to reproduce the behavior:
1. set http_proxy=http://127.0.0.1:8080
2. set https_proxy=http://127.0.0.1:8080
3. cloudflared.exe tunnel create tunnel123
4. See error
```
^C
C:\temp>set HTTP_PROXY=http://127.0.0.1:8888

C:\temp>set HTTPS_PROXY=http://127.0.0.1:8888

C:\temp>cloudflared.exe tunnel create tunnel123
failed to create tunnel: Create Tunnel API call failed: REST request failed: Post "https://api.cloudflare.com/client/v4/accounts/f85fc2f0f911ee8a7ea0c9e52a182386/cfd_tunnel": context deadline exceeded
```
No request is recevie

**Expected behavior**
It should be able to make a tunnel
**Environment and versions**
- OS: Windows
- Architecture: x64
- Version: cloudflared version 2023.8.2 (built 2023-08-31-1504 UTC)

**Logs and errors**
If applicable, add logs or errors to help explain your problem.

**Additional context**
Seems to have so many request but evey time the coversation is divereted towards SOCKS. I am talking specifically about HTTP and HTTPS proxy. Secondly, I know --protocol http2 is limited, but can I still run it through HTTP proxy if possible ?