- Update env files to include zstandard

- Update set_task_result in compute api and client to handle base64
encoded data. Rather than JSON serialize the ProtocolDAGResult (PDR)
and use this is a the intermediate format, instead:

1) create a keyed chain representation of the PDR

2) JSON serialize this representation

3) compress the utf-8 encoded bytes with zstandard

4) encode with base64

- Use the above base64 encoded data as the intermediate format and
reverse the operations above to recover the PDR.

Use more bytes

Move compression and decompression functions to new module

Use latin-1 decoded bytes

If a decompression error is raised, assume that the original data was
never compressed.

Test getting extends ProtocolDAGResults as if they were stored through
the old pdr.to_dict() -> json -> utf-8 encoded format. The new test
can be removed in the next major release that drops the old format.

To allow for better and clearer testing of result pushing and pulling,
the act of executing a task and pushing its results were separated.

Code coverage was artificially low due to run test run order. A reset
and reinitialization of the s3os_server shows the correct results.

It's more robust to paramterize the old tests to use the legacy kwarg
for pushing results rather than writing a new test that covers less of
the codebase.

…otocoldagresult