[Enhancement] remove partition version check in plan validation (backport #46733)

[mergify]

Why I'm doing:

In a large number of real-time import scenarios, if a complex query contains multiple tables, verifying the partitioned versions of multiple tables may still cause the plan to fail.

What I'm doing:

When the partition is shallow copied, the version number is copied while holding the lock, and the historical snapshot version can be used for query. So we can remove this partition version check.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

---

This is an automatic backport of pull request #46733 done by [Mergify](https://mergify.com). ## Why I'm doing: In a large number of real-time import scenarios, if a complex query contains multiple tables, verifying the partitioned versions of multiple tables may still cause the plan to fail. 

What I'm doing:

When the partition is shallow copied, the version number is copied while holding the lock, and the historical snapshot version can be used for query. So we can remove this partition version check.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

[mergify]

Cherry-pick of 8b91707 has failed:

On branch mergify/bp/branch-2.5/pr-46733
Your branch is up to date with 'origin/branch-2.5'.

You are currently cherry-picking commit 8b9170718d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   fe/fe-core/src/main/java/com/starrocks/transaction/OlapTableTxnLogApplier.java
	modified:   fe/fe-core/src/test/java/com/starrocks/planner/QueryPlanLockFreeTest.java

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   fe/fe-core/src/main/java/com/starrocks/catalog/OlapTable.java
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/sql/OptimisticVersion.java
	both modified:   fe/fe-core/src/main/java/com/starrocks/sql/StatementPlanner.java
	both modified:   fe/fe-core/src/test/java/com/starrocks/lake/LakeTableTest.java
	deleted by us:   fe/fe-core/src/test/java/com/starrocks/sql/OptimisticVersionTest.java

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr

[sonarcloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud