Prior art: authzed/spicedb#2449
The idea is that because this is a client binary that we distribute, we probably want to keep it within a reasonable size, and be aware of any one dependency that balloons the size of the binary.
Ideally we'd run this in CI and it would produce a report of some sort and fail if it's above a certain threshold; it'd be nice too if there was a way to have it report how much a change increased or decreased the binary size (which could be ignored under most circumstances).