[Feature]: Update data migration with new key sharding logic for range partition.

[yi-xmu]

Maintain the range size in ccmap during bucket migration.

• 1. Fetch the range size from storage as the base range size in the new bucket node group after data migration finished.
  Specifically, during the post commit process, the corresponding range size information is initialized on the relevant cores of the bucket new owner node group.
  Actually, this is not necessary.
• 2. Remove the range size info from the ccmap from old bucket owner node group.
  Specifically, after kickout range data for migration, the range size information for the corresponding range ID is deleted.
• 3. Update the forward logic for the keys written in the "double-write" phase.
• 4. Update log replay for data migration.