chore(meta): make vnodes sequential in initial hash mapping

[xx01cyx]

What's changed and what's your intention?

Summarize your change

Alter strategy of assigning vnodes to parallel unit when generating vnode mappings, so that initial vnode mapping will look like:

[1,1,1,1,2,2,2,2,3,3,3,3,4,4,4]

instead of

[1,1,1,2,2,2,3,3,3,4,4,4,1,2,3]

In this way:

• The compression could achieve better effects.
• It looks prettier.

Checklist

• All checks passed in ./risedev check (or alias, ./risedev c)

[codecov]

Codecov Report

Merging #3263 (1c2b6e3) into main (c824303) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3263      +/-   ##
==========================================
- Coverage   73.22%   73.22%   -0.01%     
==========================================
  Files         747      747              
  Lines      101892   101888       -4     
==========================================
- Hits        74614    74608       -6     
- Misses      27278    27280       +2     

Flag	Coverage Δ
rust	73.22% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/meta/src/manager/hash_mapping.rs	97.35% <100.00%> (-0.04%)	⬇️
src/meta/src/barrier/mod.rs	69.94% <0.00%> (-0.30%)	⬇️
src/common/src/types/ordered_float.rs	24.70% <0.00%> (-0.20%)	⬇️

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more