[kv] Fix out of order exception after delete a not exist row

[swuferhong]

Purpose

Linked issue: #230

This pr is aims to fix the OutOfOrderSequenceException after delete a not exist row or input keys with MergeEngine set to FIRST_ROW. The reason of this problem is that the kvRecordBatch send from client may not generated any CDC logs,
for example, when client attempts to delete some non-existent keys or MergeEngine set to FIRST_ROW. In this case, the old implements will simply return but not update batchSequence, as doing so would cause a OutOfOrderSequenceException problem. Therefore, this pr will introduce a filed lastOffsetDelta in record batch used to calculate the lastOffset of the current batch as: [lastOffset = baseOffset + LastOffsetDelta] instead of [lastOffset = baseOffset + recordCount -1]. The reason for introducing this field is that there might be cases where the offset delta in batch does not match the recordCount. For example, when generating CDC logs for a kv table and sending a batch that only contains the deletion of non-existent kvs, no CDC logs would be generated. However, we need to increment the batchSequence for the corresponding writerId to make sure no {@link OutOfOrderSequenceException} will be thrown. In such a case, we would generate a logRecordBatch with a LastOffsetDelta of 1 but a recordCount of 0.

Tests

API and Format

Documentation

[swuferhong]

@wuchong @luoyuxia pr ready.