Properly update response in openvsx proxy

[jeanp413]

Description

Updates response when it's compressed

Related Issue(s)

Fixes #

How to test

1. Open a workspace
2. Run NODE_DEBUG=http,https,tls /ide/node /ide/out/server-main.js --install-extension znck.vue --do-not-sync --log trace 2> debug.log in terminal
3. Check in debug.log file that only requests to the openvsx proxy are made and extensions are installed sucessfully
4. Install extensions manually using UI, check extensions are installed sucessfully

Release Notes

NONE

[akosyakov]

@jeanp413 openvsxorg.blob.core.windows.net is reliable and it is fine to connect to it directly to fetch vsix files, only requests to open-vsx.org are problematic and should always go through OpenVSX proxy. We don't watch to cache vsix files, but only requests to open-vsx.org necessary to resolve them.

[akosyakov]

@jeanp413 openvsxorg.blob.core.windows.net is reliable and it is fine to connect to it directly to fetch vsix files, only requests to open-vsx.org are problematic and should always go through OpenVSX proxy. We don't watch to cache vsix files, but only requests to open-vsx.org necessary to resolve them.

Sorry for the noise, after testing it does behave as I described. I was confused by mentioning of openvsxorg.blob.core.windows.net.

[akosyakov]

@iQQBot @mustard-mh the changes seem to do the job, it would be good if you could review go code

[iQQBot]

go code looks good

/hold

Only in the original code there are a lot of conversions between []byte and string, some of which are not necessary, bytes have almost the same methods as strings, as well as Count, Replace, etc., but these are not included in this PR

feel free to unblock

[akosyakov]

It also works well for me.

[jeanp413]

/unhold