Handle manual proxy configuration errors more gracefully

[byjrack]

Tell us about your request
Currently if a user manually configures the proxy and they are in an org that uses sign-in enforcement (allowedOrgs) they can lock themselves out if they enter something wrong into the Settings.

I have had users fat finger urls, schemes, and ports. On some releases of DD a lockout still allows the Settings panel to be opened and corrected. On some versions though the UI is completely masked and they are stuck in a loop. Manual fix in settings.json is the only option at that point.

Which service(s) is this request for?
Docker Desktop

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Users make mistakes and hand editing files is a mess. If backend can't access the proxy (timeout, 407, 403, etc) than it needs to allow for updating the Settings for Proxy and not just fail and prompt to retry. Folks likely won't know they screwed up their manual config so even if the Settings UI is accessible they don't know the issue since host side doesn't indicate an issue with backend using the proxy as configured.

Are you currently working around the issue?
KB around triaging the issue (login loop) and how to update in UI or in settings.json on platforms.