Enable proxy support for DevWorkspaces

[amisevsk]

Description

Currently, DevWorkspaces have no way to specify proxy settings, so built-in containers such as project-clone will fail to clone projects if running behind a proxy. We need to define a way to specify proxy settings and figure out how to propagate these down to the workspace pods.

Additional context

Originally brought as a CRW integration issue: https://issues.redhat.com/browse/CRW-2473

[amisevsk]

cc: @ibuziuk @l0rd this is likely a milestone 3 issue

[l0rd]

Milestone 3 issue for that was: eclipse-che/che#20386

This is mainly about injecting environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY and mounting the trusted certificates bundle. Che operator should do the heavy lifting: create the ConfigMaps containing variables and bundle in users namespaces. Then the DevWorkspace should mount them in workspaces containers. That should already work. @skabashnyuk hasn't that work been completed yet?

[skabashnyuk]

in Eclipse Che we have this eclipse-che/che-operator#1027

[metlos]

yes, mounting of proxy settings to workspace containers should already work. This issue is about supporting that also in built-in containers, is that right? I am al little bit out of the loop on DWO capabilities, so I didn't realize project clone happens in DWO and so is affected by this, too.

[l0rd]

@metlos cloning happens in initContainers, the mechanism that works for regular containers should work for init containers too.