Write proper end-to-end tests for all binaries

!22 (merged) landed a new set of tests that exercise the binaries with real use-cases.

For expedience, some of the binary tests were stubbed out with a build_test.

Running bazelisk query 'attr("tags", "[\\[ ]stub[,\\]]", tests(...))' in the e2e directory will list any tests that are currently stubbed out.

This ticket is to track implementing all those tests. There may be binaries that a impossible to test because they require certain system resources that we cannot feasibly mock.

I've added a few MRs that link to this ticket showing examples of how to write the binary tests.

They can be used as patterns for writing tests for each binary.

Please add this ticket into the MR description so they all get linked into this ticket.

I would encourage one commit per binary test and, ideally, one MR for a binary test or family of binaries. Each binary is tested in a individual directory so easy to add to the merge train.