Add ZooKeeper as the metadata storage component of TubeMQ

[gosonzhang]

Description

The parent issue is: #2281

According to the conclusions we discussed before[1], we will start the transformation of the metadata storage side of TubeMQ in the next version, and will add the ZooKeeper component as the default storage component; due to the compatibility of historical versions, the current implementation of berkeleydb-je will be retained and exists as an optional component that can be selected by the user.

1. https://lists.apache.org/thread/xdq56lw863z4kw6s73otn0ohdzhmc14g

• [TubeMQ] Add metadata backup cli script #2776
• [TubeMQ] Implement the ZooKeeper-based metadata Mapper class #2844
• [TubeMQ] Adjust the offsetstorage and zookeeper package paths #2955
• [TubeMQ] Modify the code style problems of the metadata classes #2980
• [TubeMQ] Adjust the implementation classes under the impl.bdbimpl package #3029
• [TubeMQ] Optimize the MetaStoreService implementation class #3035
• [TubeMQ] Optimize the AbsXXXMapperImpl implementation classes #3093
• [TubeMQ] Add MetaStoreMapper related implementation #3105
• [TubeMQ] Optimize the implementation of KeepAlive Interface #3108
• [TubeMQ] Optimize Metadatamanager class implementation #3143
• [TubeMQ] Adjust the Master.ini file reading implementation #3154
• [TubeMQ]Replace the call of MetaDataManager with DefaultMetaDataService #3254
• [TubeMQ] Fix some bugs when metadata is saved to ZooKeeper #3268
• [TubeMQ]Optimize CliMetaDataBRU class implementation #3324
• [TubeMQ]Update master.ini configuration guidelines document #3354
• [TubeMQ]Added how to use optional BDB components and documentation #3363

[gosonzhang]

It's been a while, let's deal with this issue

[gosonzhang]

This issue is completed, if problems are found later, they will be handled through a separate issue