[IOTDB-2559][IOTDB-1840][IOTDB-2215][IOTDB-2216] Persistent Schema Management

[MarcosZyk]

Description

Docs

All related docs are in the shared folder linked by the following url.
https://y8dp9fjm8f.feishu.cn/drive/folder/fldcnoxcC1ZU9Ux43DCfImzXYqg?from=from_copylink

Implement MTree Cache Framework

1. Rewrite attribute children management in MNode and implement MNodeContainer
2. Separate service and store of MTree
   1. implement MemMTreeStore and CachedMTreeStore for memory mode and persistent mode respectively
   2. rewrite service logic in MTreeBelowSG and Traverser based on the persistent mode
3. Implement CacheManager for CachedMTreeStore
   1. implement cache framework and two cache strategy, plain and LRU
   2. implement Pin/Unpin to manage mnode cache and buffer

Implement SchemaFile

1. Implement mnode operations
2. Implement page space management

Currently, we have not ensured the consistency and reliance of schemafile when encountering unexpected abort. It could be understand as we extend the workspace of metadata from memory to disk. Now we still recover SchemaRegion based on redoing mlog.

New config parameters

1. enable_persistent_schema: whether to use persistent schema mode
2. cached_metadata_size_in_persistent_mode: the memory used for metadata cache when using persistent schema, currently this represents the num of cached mnode
3. max_schema_flush_thread: the max num of thread used for flushing metadata to schema file
4. minimum_schema_file_segment_in_bytes: the minimum size (in bytes) for segment inside a schema file page
5. page_cache_in_schema_file: the cache size for schema page in one schema file

Future work

implement SchemaRegion recover based on schemafile

[coveralls]

Coverage decreased (-2.3%) to 65.428% when pulling 0f3c1a7 on MarcosZyk:persistent_schema into 3f915d0 on apache:master.