feat(rocksdb): Use original CreateCheckpoint and read meta data from meta CF

[acelyc111]

What problem does this PR solve?

Ref: #468
We have store meta data(Pegasus data version, last manual compact timestamp, decree) both in RocksDB's manifest and meta column family in version 2.0.0, now we are going to read meta data from meta CF instead of manifest.
Main changes of this PR:

• Validate meta CF existence when DB exist (means only allowed to upgrade from 2.0)
• Read meta data from meta CF
• Do checkpoint by rocksdb's original APIs.

NOTE: Since meta data is still wrote into manifest, so there is no compatibility problems with 2.0.0.

What is changed and how it works?

No user faced changes.

Check List

Tests

• Manual test (add detailed scripts or steps below)

1. Upgrade from 1.x.x
   Will fail, only allowed from version 2.0.x
2. Upgrade from 2.0.0

• Deploy a cluster in version 2.0.0
• Write some data
• Upgrade to this commit's version
• Read these data successfully

Code changes

• Has exported function/method change
  No
• Has exported variable/fields change
  No
• Has interface methods change
  No
• Has persistent data change
  No

Side effects

• Possible performance regression
  No
• Increased code complexity
  No
• Breaking backward compatibility
  No

Related changes

• Need to cherry-pick to the release branch
  Yes
• Need to update the documentation
  Yes
• Need to be included in the release note
  Yes