Updater lack proxy configuration

[k79e]

Description

The updater don't use proxy as main program.

Steps to reproduce

Set a http proxy e.g. --proxy-server=http://.....
And run program.
Then I find updater is using direct connection to check the update.

Describe how what happens differs from what you expected.

The updater should use proxy same as main program but it's not.

Logs being sent: yes/no

Version information

• Platform: desktop

For the desktop app:

• OS: Windows, macOS, Ubuntu, Arch Linux, etc?
• win7 x64
• Version: 1.x.y
• 1.7.29

[NHAS]

Hijacking this issue somewhat to give context to a pull request that would solve this.

Context from PR comments thread:

While element itself can use the electron --proxy-server option, this is not applied to the autoupdater which may lead to privacy issues as discussed previously in this issue.
Lacking this functionality also makes it harder to deploy these changes at scale.

For example, imagine a private matrix server that is behind a proxy, currently if we want to set up a number of devices to use it we would have to add a command line argument when Element is executed, which isnt standardised across multiple platforms (Im looking at you Mac).
Even with that argument added the auto updater will still dial out to the internet. Which may be not what users want.

[NHAS]

@k79e Hey, the pull request that I've linked will add proxy support via config file to Element. Would it be possible for you to update the name of this issue to "Element lacks proxy configuration" or something similar, just so it can represent the pull request as well.

If not. All goods!