Consider binary deployment process and versioning

When XCHammer was originally implemented, the goal was to version program along with each commit. The point of versioning _every_ tooling dependency is to ensure that a given commit can build: _I don't want to checkout a commit and not have the right version of X program.._

Currently, this is achieved by checking in the binary. At a few MB, it really isn't that big of a deal, but we could do better.

Consider how this approach will work:
1) Do trusted CI builds for each commit
2) Github binary releases for each build
3) Load the binary with other systems like `nix` and `Bazel`

All of these may have implications on runtime performance of builds, as we run XCHammer constantly. Consider how this change would manifest end to end. Take an opinionated stance, don't force a process on users, but make it easy and documented.