Implement compression with Tower layer

[daxpedda]

This replaces the hand-written compression implementation with a Tower layer provided by tower-http.

This gets us a couple of improvements:

• More compression algorithms, including Brotli, which is usually better then gzip.
• All files are now being automatically compressed.
• Less code 🎉.

Disadvantages:

• Explicitly state that the size listed is the compressed size #6 was thrown out the window.
• Pulling in more dependencies, this can be fixed by deciding for only one algorithm instead of all three.

[daxpedda]

Rebased after #14.

[daxpedda]

Rebased after #13.

[jakobhellermann]

While this is much nicer from an implementation perspective, I decided against doing this because I really wanted to be able to print a representative size of how large a compressed wasm binary would be, which didn't work nicely with just having a generic tower compression layer.

If we want to do compression for other files (e.g. html) or other formats (e.g. brotli) then we can consider that separately in other PRs/issues.