[BugFix] Fix pushdown subfield with unstrict expression in project error (backport #51100)

[mergify]

Why I'm doing:

For unstrict expression with semi-type, e.g: coalesce(array...)/ifnull(array...), will push down the whole expression cross outer join, it's the wrong way, will take the result error
we should only push down array expression, not coalesce(array...), coalesce shoule stay in place

What I'm doing:

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 #51100 done by [Mergify](https://mergify.com). ## Why I'm doing:

For unstrict expression with semi-type, e.g: coalesce(array...)/ifnull(array...), will push down the whole expression cross outer join, it's the wrong way, will take the result error
we should only push down array expression, not coalesce(array...), coalesce shoule stay in place

What I'm doing:

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 2a85b7c has failed:

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

You are currently cherry-picking commit 2a85b7cb61.
  (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/sql/optimizer/rule/tree/CloneDuplicateColRefRule.java
	modified:   fe/fe-core/src/test/java/com/starrocks/sql/optimizer/rule/transformation/materialization/MvRewriteTest.java
	modified:   fe/fe-core/src/test/java/com/starrocks/sql/plan/AggregateTest.java
	modified:   fe/fe-core/src/test/resources/sql/tpch-histogram-cost/q14.sql
	modified:   fe/fe-core/src/test/resources/sql/tpchcost/q14.sql

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   fe/fe-core/src/main/java/com/starrocks/sql/optimizer/rule/tree/prunesubfield/PushDownSubfieldRule.java
	both modified:   fe/fe-core/src/main/java/com/starrocks/sql/optimizer/transformer/SqlToScalarOperatorTranslator.java
	both modified:   fe/fe-core/src/test/java/com/starrocks/sql/plan/LowCardinalityTest.java
	both modified:   fe/fe-core/src/test/java/com/starrocks/sql/plan/PruneComplexSubfieldTest.java
	both modified:   fe/fe-core/src/test/resources/sql/external/hive/tpch/q14.sql
	deleted by us:   fe/fe-core/src/test/resources/sql/scheduler/tpch/q14-2.sql
	deleted by us:   fe/fe-core/src/test/resources/sql/scheduler/tpch/q14.sql

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
23 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