I do not know why.

If you are not using nix then you'll have to figure it out yourself, sorrrrryy.

`cabal run tests` sometimes fails with an error about the build plan not
including the test suite :(  but we can make sure the plan includes the test
suite with this flag.

fixes for base64 issues

we need to use an _even older_ version of ghc than we're using now and
modern-uri doesn't seem particularly amenable to that.

network-uri is perfectly fine, anyway.

And it only tells us what cabal tells us later, packages are broken...

fresh start

reduce closure size etc

Tell cabal to configure zlib a certain way when building it, making its build
errors go away without changing our own cabal package configuration.

`cabal list-bins ...` might output some garbage before outputting the path, so
this breaks :/  Also why do it the hard way when we can do it the easy way!

I almost used it to narrow these two dependencies to library-only but it turns
out to not make much difference so it doesn't seem worth the extra complexity
now.

However, having access to the library might prove useful in the future.

Each generated with `cabal2nix https://.../` and then mangled by alejandro

These give us the network protocol for downloading, the framing protocol for
decoding, and the cryptographic protocol for decrypting