[Bug](rebanlace) resolving data inconsistencies caused by rebanlace

[zhuxiangyi]

What problem does this PR solve?

• A rebalance occurred during data load from the broker, causing inconsistency between the two replicas.
• The rebalance only checked PRMITTED (not COMMITTED). Since no PRMITTED was found, the rebalance was allowed, and cloning began, using visibleVersion as the baseline.
• During execution, the source replica contained data that was COMMITTED but not VISIBLE. The clone, using visibleVersion, did not include this data. The new replica lacks this data.

Added checks for COMMITTED but not VISIBLE transactions; changed from table-level checks to partition-level checks.

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?