Add some rocksdb new feature

[caipengbo]

#209 proposed some optimization points for RocksDB, and I tried to apply them to Kvrocks through some research.

Here are my optimizations:

1. Dynamic resize block and SST introduced by dynamic resize block and sst #120 and Support the auto-resize-block-and-sst config directive #289 to deal with the problem of large index/filter blocks.

   This mechanism resize target_file_size_base and block_size by calculating the average key-value size:

   https://github.com/KvrocksLabs/kvrocks/blob/782c106d4513eb79a94431f0750a626c26b1fdd2/src/server.cc#L1050

   It uses the compressed total size to calculate the average key-value, which can easily be less than 128, resulting in target_file_size_base always be 16. When there is a large amount of data, a large number of SST files are generated. Too many files may cause problems.

   Therefore, I use Partitioned Index/Filter to deal with large Index/Filter blocks and remove autoResizeBlockAndSST() . Through some test, I found that when our files were large(128M), we did not generate large index/filter blocks to increase the long tail latency.

2. Add Rocksdb's new feature integrated BlobDB(Since 6.18.0) for large value scenarios. Although the integrated BlobDB has not been announced for production yet, I think it can be added for users to test.

[git-hulk]

Really good feature, some users also look forward to the blob store. #366

[caipengbo]

By the way, I will solve #384

[ShooterIT]

LGTM, just minor comments

[ShooterIT]

Please also do some surveys on memtable_prefix_bloom_size_ratio and memtable_whole_key_filtering.
i think for metadata CF, there are most point lookup, it is a good idea to enable memtable filter, for subkey CF, it may not, sine users may execute lrange hgetall zrangeXX commands that use range lookup.

[caipengbo]

Please also do some surveys on memtable_prefix_bloom_size_ratio and memtable_whole_key_filtering.
i think for metadata CF, there are most point lookup, it is a good idea to enable memtable filter, for subkey CF, it may not, sine users may execute lrange hgetall zrangeXX commands that use range lookup.

Yes, I haven't noticed this optimization yet, I will investigate it later.

[ShooterIT]

Summary of this PR

• Support blob db (key-value separation) which requires RocksDB version greater than 6.18
• Enable partitioned index/filter for SST and hash index for data block
• Enable whole key filter for memtable
• Remove dynamic resize block and SST
• Only apply compression to SST which level is more than 2

@caipengbo do i miss something?

[caipengbo]

Summary of this PR

• Support blob db (key-value separation) which requires RocksDB version greater than 6.18
• Enable partitioned index/filter for SST and hash index for data block
• Enable whole key filter for memtable
• Remove dynamic resize block and SST
• Only apply compression to SST which level is more than 2

@ShooterIT It's a complete summary!