[Hub] Cannot download/install Unity from behind proxy on Linux

When trying to install/download Unity versions via Hub on Linux, the process will fail and errors will be logged (errors will follow below).

It is worth noting this issue was observed when working with a packet sniffer with a trusted root CA installed along side the proxy, which may be the source of the problem if it is determined to be certificate related. Hub's authentication is still working as is all other connectivity/applications on the machine. Environmental variables have also been set appropriately for use with a proxy.

'Something went wrong with downloadUnityEditor',\n { Error: tunneling socket could not be established, cause=connect EINVAL 0.0.34.184:80 - Local (0.0.0.0:0)\n at ClientRequest.onError (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/tunnel-agent/index.js:177:17)\n at Object.onceWrapper (events.js:316:30)\n at emitOne (events.js:115:13)\n at ClientRequest.emit (events.js:210:7)\n at Socket.socketErrorListener (_http_client.js:401:9)\n at emitOne (events.js:115:13)\n at Socket.emit (events.js:210:7)\n at emitErrorNT (internal/streams/destroy.js:64:8)\n at _combinedTickCallback (internal/process/next_tick.js:138:11)\n at process._tickCallback (internal/process/next_tick.js:180:9) code: 'ECONNRESET' }

and

'Error while trying to install a custom editor: RequestError: Error: Invalid protocol: 127.0.0.1: RequestError: Error: Invalid protocol: 127.0.0.1:\\n at new RequestError (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request-promise-core/lib/errors.js:14:15)\\n at Request.plumbing.callback (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request-promise-core/lib/plumbing.js:87:29)\\n at Request.RP$callback [as _callback] (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request-promise-core/lib/plumbing.js:46:31)\\n at self.callback (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request/request.js:185:22)\\n at emitOne (events.js:115:13)\\n at Request.emit (events.js:210:7)\\n at Request.init (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request/request.js:458:17)\\n at Request.RP$initInterceptor [as init] (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request-promise-core/configure/request2.js:45:29)\\n at new Request (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request/request.js:127:8)\\n at request (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/request/index.js:53:10)\\n at Releases._fetchIniFile (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/@unityhub/hub-generate-releases/src/releases.js:220:20)\\n at Releases.getReleaseInfoPerPlatform (/tmp/.mount_UnityHuvEtK7/resources/app.asar/node_modules/@unityhub/hub-generate-releases/src/releases.js:193:29)\\n at Releases._getReleaseInfoPerPlatform (/tmp/.mount_UnityHuvEtK7/resources/app.asar/src/services/editorManager/unityReleaseService.js:121:14)\\n at Releases.fetchReleaseInfo (/tmp/.mount_UnityHuvEtK7/resources/app.asar/src/services/editorManager/unityReleaseService.js:116:17)\\n at Releases.setCustomEditorInfo (/tmp/.mount_UnityHuvEtK7/resources/app.asar/src/services/editorManager/unityReleaseService.js:94:17)\\n at UnityHubProtocolHandler.handleUrl (/tmp/.mount_UnityHuvEtK7/resources/app.asar/src/unityhubProtocolHandler.js:32:20)'

Steps to reproduce:
1- Configure linux for use with a proxy
2- Launch Hub
3 - Trigger an installation via Hub or a Hublink
4- Observe the installation will fail and the user will be returned to the Unity installation view
5- Locate togs in ~/.config/UnityHub/logs/info-log.json
6- Observe logged errors