Move IoTConsensus multi-data-dir region migration ITs to commit suite

[hongzhi-gao]

Description

Content1

Move IoTConsensus multi-data-dir region migration ITs from pass/daily/iotv1 to pass/commit, updating package names and static imports so they run in the commit CI suite instead of daily.

Content2

Fix IoTDBMigrateMultiRegionForIoTV1IT.multiRegionMigrateTest, which failed in ClusterIT (1C3D) because INSERTION1 only creates one schema region and one data region; with replication factor 1 they are often placed on different DataNodes, so no DataNode hosts two regions. Before multi-region migrate, colocate regions via extend region when needed.

---

This PR has:

• been self-reviewed.
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods.
• added or updated version, license, or notice information
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage.
• added integration tests.
• been tested in a test IoTDB cluster.

---

Key changed/added classes (or packages if there are too many classes) in this PR

• org.apache.iotdb.confignode.it.regionmigration.pass.commit — 3 IT classes moved from pass.daily.iotv1:
  • IoTDBRegionMigrateWithDeletionMultiDataDirIT
  • IoTDBRegionMigrateWithDeletionMultiDataDirTableIT
  • RegionMigrateFileAssertions
• IoTDBMigrateMultiRegionForIoTV1IT — fix region colocation before multi-region migrate

Test plan

• IoTDBRegionMigrateWithDeletionMultiDataDirIT (ClusterIT)
• IoTDBRegionMigrateWithDeletionMultiDataDirTableIT (TableClusterIT)
• IoTDBMigrateMultiRegionForIoTV1IT (ClusterIT)