[ReshardingV3] State

[staffik]

We agreed to use the mapping strategy (design doc).

Implementation plan:

• Initial implementation: https://github.com/near/nearcore/pull/12084
  • Add persistently stored shard_uid mapping.
  • Use the mapping in Store::get() for State column.
  • Prohibit prefix or range iter methods with State column.
• Use the mapping in update operations + add unit tests: https://github.com/near/nearcore/pull/12232
• Integration + testloop: https://github.com/near/nearcore/pull/12269
• Handle copy_state_from_store in cold_storage.rs (see comment).
• Handle range iter in load_one_subtree in parallel_loader.rs.
• State clean up (e.g. gc parent state when it is no longer referenced by any child), see https://github.com/near/nearcore/issues/11883.
• Profiling (see doc), testing.