What does this PR do?

What issues does this PR fix?

How to test this PR?

1. Start mitmproxy on the host:

   mitmdump --listen-port 8080

2.1 Set your token in the command below
2.2 Run the che-code container with proxy settings and the mitmproxy CA:

podman run --rm -it -p 3100:3100 \
-e CODE_HOST=0.0.0.0 \
-e HTTPS_PROXY=http://host.containers.internal:8080 \
-e HTTP_PROXY=http://host.containers.internal:8080 \
-e NODE_EXTRA_CA_CERTS=/public-certs/mitmproxy-ca.crt \
-e GITHUB_TEST_TOKEN=token \
-v ~/.mitmproxy/mitmproxy-ca-cert.pem:/public-certs/mitmproxy-ca.crt:ro \
quay.io/rnikitenko/che-code:pr-145-arm64  

3. Open the editor in a browser (incognito window) at http://localhost:3100 (see URL in the command output).

4. F1 => Test GitHub Proxy (axios) => see notification and check logs(which mechanism is used? the main? the fallback?) in the che-api output

6. Run the editor on openshift => Trigger any flow that calls che-api's GithubService.getUser() (e.g. the Device Authentication flow after completing GitHub OAuth).

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder