It should be possible to configure operator to ignore OpenShift cluster-wide proxy config

[amisevsk]

Description

On OpenShift clusters, the DevWorkspace Operator reads the cluster proxy and uses values from there to configure httpProxy, httpsProxy, and noProxy for itself and workspace containers. The DevWorkspace Operator Config CR can additionally be used to override httpProxy and httpsProxy, and to add values to noProxy, but there is no convenient way to override these fields to be unset -- setting e.g. httpProxy to "" will result in DWO treating the field as if it were unset, continuing to use the cluster-detected value.

Instead, setting any proxy field to the empty string ("") should result in DWO ignoring any values detected from the cluster.

Currently, there is a workaround: if the field is set to " " (i.e. whitespace only), DWO will use this value for proxy environment variables, effectively not propagating proxy configuration into workspaces.

Additional context

N/A