method to disable transport compression

[kris-watts-gravwell]

Enhancement

What is the enhancement to be made?

cloud archive clients currently compress shards when they send them to the archive server using transport compression, add method to disable this on the client and signalling headers on the server to detect if/when we should enable that transport decompression.

Why should we make this change? (Business justification? What problem is the feature trying to solve?)

Transport compression was originally implemented because we assumed that the cloud archive server would be in a remote cloud, so minimizing transport bandwidth usage was useful.

However, in local instances this just chews a ton of CPU and memory, we should enable the ability to disable this transport compression.

Any other comments?

Figure out how to make this backwards compatible so that users do not have to force upgrades on cloud archive servers.