autoProxy=true not creating https / no_proxy variables (as reported in #11551 )

Nobody has claimed this yet.

### Windows Version

Microsoft Windows [Version 10.0.22631.4602]

### WSL Version

2.3.26.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

5.15.167.4-1

### Distro Version

_No response_

### Other Software

### Repro Steps

1. Configure .wslconf with
```
[wsl2]
autoProxy=true
```

2. run wsl

3. check environment variables

### Expected Behavior

WSL to configure http and https proxy variables as stated here: [WSL Troubleshoot](https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#considerations-when-using-autoproxy-for-httpproxy-mirroring-in-wsl)

> When enabled, the following apply to proxy settings on your Linux distributions:
> The Linux environment variable, HTTP_PROXY, is set to the one or more HTTP proxies found installed in the Windows HTTP proxy configuration.
> The Linux environment variable, HTTPS_PROXY, is set to the one or more HTTPS proxies found installed in the Windows HTTP proxy configuration.
> The Linux environment variable, NO_PROXY, is set to bypass any HTTP/S proxies found in the Windows configuration targets.
> Every environment variable, except WSL_PAC_URL, is set to both lower case and upper case. For example: HTTP_PROXY and http_proxy.

### Actual Behavior

Only http_proxy, HTTP_PROXY and WSL_PAC_URL are being created on wsl.

```
env | grep -i http
http_proxy=http://example.com:3128
HTTP_PROXY=http://example.com:3128
WSL_PAC_URL=http://example.com/wpad.dat
```

### Diagnostic Logs

will be sent by email

No source file, test, or entry point is named. Start by reproducing the issue with [wsl2] autoProxy=true on WSL 2 and inspect the environment variables, then review the diagnostic information requested in the issue. Done means HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and their lowercase forms are configured as described, alongside WSL_PAC_URL.

Written by the indexing model from the issue text.