fix crash when schema version is greater than 255

[critical27]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

#3889

Description:

Crash because of out-of-range access in vector.
The byte order of schema version in meta is not same as numerical order.

version	(INT64_MAX - version) in hex	rocksdb (INT64_MAX - version) little endian
0	ff ff ff ff ff ff ff ff	ff ff ff ff ff ff ff ff
1	ff ff ff ff ff ff ff fe	fe ff ff ff ff ff ff ff
...	...	...
255	ff ff ff ff ff ff ff 00	00 ff ff ff ff ff ff ff
256	ff ff ff ff ff ff fe ff	ff fe ff ff ff ff ff ff
...	...	...

The output order in rocksdb when we prefix scan is quite complicated, just say a simple example with 257 schema versions in range [0, 256], the order will be: 255 254 253 ... 3 2 1 256 0

How do you solve it?

Just resize to make sure the vector is valid.

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:
Bug fix, fix crash when schema versions are more than 256

[critical27]

Talked with @yixinglu offline, forbid the Gherkin format check now

[pengweisong]

Good job~