In the LevelDB encoding, the internal key can be cut at any byte:
including the user_key, type, or sequence_number. The resulting prefix
is shared among subsequent keys and not specified explicitly by them.
This fixes a previous mistaken belief that cuts can't happen in the
last 8 bytes of the type & sequence number.
Tests are added.