Standardize to dotnet archive compression libraries

[jaredbroad]

Expected Behavior

A single clean interface for working with archives

Actual Behavior

Many different libraries are used in LEAN for various Compression methods; all of them copying to memory instead of streaming due to mono issues.

Potential Solution

Careful/thoughtful testing and exploration of an archive abstraction, similar to presented here (#2416). Ideally with focus on the application and hiding the library implementation.

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

[Martin-Molinero]

Believe we need this issue to be solved dotnet/runtime#1544

[Martin-Molinero]

We are currently using 2 libraries because the backend is using an append functionality to existing zip entries which did not work correctly using a single library.
Since there's no real driver for this issue except code cleanness and it's risky we will skip it for now until dotnet compression is ready for our use cases.