Provide an option to compress HTTP responses

[ameshkov]

Issue Details

When filtering HTML pages CoreLibs decompresses them in order to filter the content. This is perfectly okay when the filtering takes place locally.

However, when the user is using AdGuard CLI on a server as a proxy server and routes the traffic through that proxy, serving uncompressed HTML pages (and local.adguard.org content as well), this creates additional bandwidth usage that we would better avoid.

Proposed solution

Provide an option to compress HTTP responses. If the option is enabled, all HTTP responses served by CLI, should be compressed. Mainly, this is important for the responses that we previously decompressed and for local.adguard.org responses.

Alternative solution

No response