api, pipeline: support compressed measurements

[bassosimone]

This issue is about accepting compressed measurements. We'll close this issue when we've implemented accepting compressed measurements on the backend side.

This issue is a follow up to ooni/probe#1802.

We discussed this matter in today's backend meeting with @FedericoCeratto and @hellais. Here are notes from the meeting regarding what we think we'll need to do to make this happen:

1. the probe needs to set a header to indicate the measurement is compressed;
2. it seems python's gzip implementation could use a context manager to limit the used memory;
3. the ooni/api does not touch the incoming measurement in any way and just stores it to disk where the upload and the fastpath will pick it up and, respectively, save it, process it and insert it into the fastpath table;
4. so the ooni/api can just receive the compressed measurement and put it into a can;
5. we need to use the filename as metadata to tell the rest of the backend the postcan is compressed;
6. the fastpath needs to know how to handle compressed measurements.

See also ooni/probe#2014.

[hellais]

Add this as a child issue of: #931. We can maybe add support for this as part of that.