Store value protobuf directly for MVCC values

Instead of storing byte strings manually and manually varint encoding
integer values for incrementable keys, we now marshal and unmarshal the
Value protobuf directly. This allows us to Get incrementable keys and
to scan them. It also allows us to correctly discern an error incrementing
a key which is not a varint encoded value.

Implemented value checksums and checksum verification, although only
doing the verification now through kv/rest. Probably want to do the
same elsewhere.
I think this is a case where it's worthwhile - the field is semantically nullable, and it's both more efficient and less confusing to represent it as such, instead of requiring anything that needs to work with the timestamp to see if it has its zero value.