[Feature] Recovering WAL records will not add schema to tskv; stores drop_table & remove_tsfamily in WAL

[zipper-meng]

Required checklist

• Sample config files updated (config,meta/config and default config)
• If there are user-facing changes, the documentation needs to be updated prior to approving the PR( Link )
• If there are any breaking changes to public APIs, please add the api change label.
• Signed CLA (if not already signed)

Which issue does this PR close?

Related #1178, but has some differences.

Rationale for this change

WAL changes

• Simplify WAL write api in kvcore.rs
• Store drop_table and remove_tsfamily in WAL files.
  • Recovering tskv from WAL write will not create database schemas, and if database&table&tsfamily of a WAL record does not exist in tskv, this WAL record will be ignored.
  • Recovering tskv from WAL drop_table or remove_tsfamily will not do anything, because WAL write that schema not existed in tskv was ignored.

Here is the newest schema of the record data in WAL file:

# type = Write
+------------+------------+------------+------------+--------------+-----------------+-----------+
| 0: 1 byte  | 1: 8 bytes | 9: 4 bytes | 13: 1 byte | 14: 8 bytes  | 22: tenant_size |  n bytes  |
+------------+------------+------------+------------+--------------+-----------------+-----------+
|    type    |  sequence  |  vnode_id  |  precision | tenant_size  |  tenant         |   data    |
+------------+------------+------------+------------+--------------+-----------------+-----------+

# type = DeleteVnode
+------------+------------+------------+-------------+-------------+----------+
| 0: 1 byte  | 1: 8 bytes | 9: 4 bytes | 13: 8 bytes | 21: n bytes | n bytes  |
+------------+------------+------------+-------------+-------------+----------+
|    type    |  sequence  |  vnode_id  | tenant_size |  tenant     | database |
+------------+------------+------------+-------------+-------------+----------+

# type = DeleteTable
+------------+------------+-------------+---------------+-----------------+---------------+---------+
| 0: 1 byte  | 1: 8 bytes | 9: 8 bytes  | 17: 4 bytes   | 21: tenant_size | database_size | n bytes |
+------------+------------+-------------+---------------+-----------------+---------------+---------+
|    type    |  sequence  | tenant_size | database_size |  tenant         |  database     | table   |
+------------+------------+-------------+---------------+-----------------+---------------+---------+

Other improves

• Fix unit tests in test_kvcore_interface.rs sometime report unexpected error: update table conflict.
• Fix some errors that holds some strings instanced too earily, for those errors that stores data in heap:
  • Use Option::ok_or_else() instead of Option::ok_or()
  • Use Result::with_context() insead of Result::context()
  • Some others.

Are there any user-facing changes?

[roseboy-liu]

• refactor the WAL mod
• add drop vnode/table entry for WAL
• support drop vnode/table recover from WAL