[BugFix] Disable date_trunc equivalent replace if binary type is LE (backport #53229)

[mergify]

Why I'm doing:

Query should be rewritten below:

 MV       : select date_trunc('day', dt) as dt from t
Query  : select date_trunc('month, dt) from t where dt between '2023-11-01' and '2023-12-01'

What I'm doing:

    /**
     * TODO: we can support this later.
     * Change date_trunc('month', dt) to col = '2023-12-01' will get a wrong result.
     * MV       : select date_trunc('day', dt) as dt from t
     * Query1   : select date_trunc('month, dt) from t dt = '2023-11-01'
     * -- cannot be rewritten, rewrite  result will be wrong
     * Rewritten: select date_trunc('month, dt) from t where date_trunc('month', dt) = '2023-11-01'
     *
     * Query2   : select date_trunc('month, dt) from t where dt between '2023-11-01' and '2023-12-01'
     * -- cannot be rewritten, dt='2023-12-01' doesn't match with date_trunc('month', dt)= '2023-11-01'
     * Rewritten : select date_trunc('month, dt) from t where date_trunc('month', dt) between '2023-11-01' and '2023-12-01'
     */

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.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

    ---

    This is an automatic backport of pull request [BugFix] Disable date_trunc equivalent replace if binary type is LE #53229 done by Mergify.

Why I'm doing:

Query should be rewritten below:

 MV       : select date_trunc('day', dt) as dt from t
Query  : select date_trunc('month, dt) from t where dt between '2023-11-01' and '2023-12-01'

What I'm doing:

    /**
     * TODO: we can support this later.
     * Change date_trunc('month', dt) to col = '2023-12-01' will get a wrong result.
     * MV       : select date_trunc('day', dt) as dt from t
     * Query1   : select date_trunc('month, dt) from t dt = '2023-11-01'
     * -- cannot be rewritten, rewrite  result will be wrong
     * Rewritten: select date_trunc('month, dt) from t where date_trunc('month', dt) = '2023-11-01'
     *
     * Query2   : select date_trunc('month, dt) from t where dt between '2023-11-01' and '2023-12-01'
     * -- cannot be rewritten, dt='2023-12-01' doesn't match with date_trunc('month', dt)= '2023-11-01'
     * Rewritten : select date_trunc('month, dt) from t where date_trunc('month', dt) between '2023-11-01' and '2023-12-01'
     */

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 3e89c4e has failed:

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

You are currently cherry-picking commit 3e89c4e7cb.
  (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/test/java/com/starrocks/sql/optimizer/rule/transformation/materialization/MvRewritePartialPartitionTest.java

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   fe/fe-core/src/main/java/com/starrocks/sql/optimizer/rule/transformation/materialization/equivalent/DateTruncEquivalent.java
	both modified:   fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewManualTest.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
0 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 SonarQube Cloud