WSL Proxy Support: First Run Dialog

[rak-phillip]

Problem Description

WSL Proxy support was added in #4300 with the inclusion of new preferences for configuring the proxy settings. We need to understand if these new proxy settings fit into the first run dialog, and how to best include them so that first run remains as lean as possible.

Proposed Solution

We still need to settle on an approach that will provide the best experience for all users. Potential options include

• Include the proxy settings on Windows for all users, hide the proxy settings behind a checkbox by default
• Attempt to determine if proxy settings need to be configured and only render the proxy settings to users who might need them
• Don't include the proxy settings in the first run dialog and allow a diagnostic to run that will alert the user to address any potential proxy configuration that is missing

Additional Information

Discusssion

https://github.com/rancher-sandbox/rancher-desktop/pull/4300#discussion_r1152592528

[jandubois]

• Don't include the proxy settings in the first run dialog and allow a diagnostic to run that will alert the user to address any potential proxy configuration that is missing

This seems to be the only possible option if the need for proxy settings cannot be determined until the VM is running:

The first run dialog is used to select the container engine and kubernetes version, so the VM is not setup until after the first-run dialog has been dismissed. So creating a diagnostics seems to be the most flexible option:

We can verify that the host has internet connectivity while the VM does not. In this case a missing proxy configuration is the likely reason.

---

I expect that proxy settings are typically an enterprise thing, in which case the administrators will hopefully use a deployment profile, so the user would never see the first-run dialog anyways (and the settings should automatically be correct).

So a related task would be to make sure that proxy settings can be configured automatically via deployment profiles (e.g. what does this mean for dynamically fetching list of proxies?).