`compress_dynamo_documents` breaks permanent environment cache

[khvn26]

If compress_dynamo_documents flag set to true, permanent environment cache (the one configured with CACHE_ENVIRONMENT_DOCUMENT_ settings) gets broken.

A correct approach would be to use a mapper with a different destination type for the cache — flagsmith_schemas.api.V1EnvironmentDocumentResponse seems appropriate, and it's already being used for the cache consuming view's API docs.

Related to #6654.

We should abstain from enabling compress_dynamo_documents for self-hosted defaults before this issue is solved.

[matthewelwell]

@khvn26 isn't a viable solution here to just not compress unless we're storing in dynamodb? We don't really care about compressing for redis, right?

In fact, as far as I can tell, this shouldn't be an issue since the logic to write the documents to redis is completely separate to the one which writes them to dynamo? See here