[BUG] The extension for VSCode can ignore http_proxy at startup

[ptomanRH]

Please refer to Jira TC-2568

Red Hat Dependency Analytics extension for VSCode, test build 0.9.6 fails to load component report when at startup of VSCode when HTTP Proxy is required (and configured). Followup requests are working - correctly using the proxy settings.

How to reproduce:

have http proxy configured in VSCode
have RHDA extension installed
open some manifest file (e.g. attached package.json, seems smaller/faster to parse file may be important, bigger pom.xml did not reproduced the issue, so likely it is timing issue)
close VSCode
start VSCode again - it will reopen the manifest file too
it automatically executes component (inline) analysis through RHDA
component analysis fails (if rhda server is not reachable directly)
alternatively it can be observed in the proxy log that it did not initiated connection for rhda
Expected outcome:

component analysis succeeds even also at vscode startup using http proxy
(observe in proxy log that it handled connection to rhda server for first request at startup too)
Workaround:

as any followup requests, after VSCode and Extensions initialized and loaded settings, do work properly through proxy
it is possible to just switch between opened files, or close/reopen the manifest file (package.json etc), extension will try again to obtain component analysis and this time it will succeed.
More verbose output can be seen in log file rhda-startup-first-no-proxy.log and as