Refactor: Remove reverts from compressor

[Tabaie]

Description

In accordance with @ivokub's feedback on #367, change the compressor's flow into one that writes on a "scratch" and in case of success copies it into the current state. This would replace the current strategy of optimistically attempting to compress and reverting if something went wrong.

Motivation

The fact that there are more ways of going wrong than going right (there are many control paths leading to a revert) has lead to complex code involving many goto-labels. The pessimistic strategy will result in smaller, more readable code.

@gbotrel thoughts?

Tasks

• Medium-level task that needs to be implemented for this feature request to be considered complete.

Acceptance criteria

• List tests that need to be implemented or checks to consider this task completed.

Risks

• These are risks that may prevent completion of the task as well as areas to pay special attention to

Remember to

• Add the documentation label in case there is an impact on the documentation
• Add priority and team labels
• Add Task for updating the Runbook or adding/updating existing metrics and alerts.