[BugFix] MV rewrite may generate wrong plans if query only contains constant call operators (backport #50757)

[mergify]

Why I'm doing:

CREATE MATERIALIZED VIEW `test_mv1` (`1`, `count(DISTINCT k2)`)
DISTRIBUTED BY RANDOM
REFRESH MANUAL
PROPERTIES (
"replicated_storage" = "true",
"replication_num" = "1",
"storage_medium" = "HDD"
)
AS SELECT 1 AS `1`, count(DISTINCT `s1`.`k2`) AS `count(DISTINCT k2)`
FROM `test`.`s1`;

mysql> explain select count(1) from s1;
+-----------------------------+
| Explain String              |
+-----------------------------+
| PLAN FRAGMENT 0             |
|  OUTPUT EXPRS:4: count      |
|   PARTITION: UNPARTITIONED  |
|                             |
|   RESULT SINK               |
|                             |
|   2:EXCHANGE                |
|                             |
| PLAN FRAGMENT 1             |
|  OUTPUT EXPRS:              |
|   PARTITION: RANDOM         |
|                             |
|   STREAM DATA SINK          |
|     EXCHANGE ID: 02         |
|     UNPARTITIONED           |
|                             |
|   1:Project                 |
|   |  <slot 4> : count(5: 1) |
|   |                         |
|   0:OlapScanNode            |
|      TABLE: test_mv1        |
|      PREAGGREGATION: ON     |
|      partitions=1/1         |
|      rollup: test_mv1       |
|      tabletRatio=2/2        |
|      tabletList=30937,30939 |
|      cardinality=1          |
|      avgRowSize=8.0         |
|      MaterializedView: true |
+-----------------------------+
29 rows in set (0.00 sec)

Query will face this error:

mysql> select count(1) from s1; 

ERROR 1064 (HY000): Vectorized engine does not support the operator, node_type: 0 backend [id=10001] [host=172.26.92.227]

What I'm doing:

• Fix mv rewrite wrong plans if query only contains constant call operators

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 #50757 done by [Mergify](https://mergify.com). ## Why I'm doing: ``` CREATE MATERIALIZED VIEW `test_mv1` (`1`, `count(DISTINCT k2)`) DISTRIBUTED BY RANDOM REFRESH MANUAL PROPERTIES ( "replicated_storage" = "true", "replication_num" = "1", "storage_medium" = "HDD" ) AS SELECT 1 AS `1`, count(DISTINCT `s1`.`k2`) AS `count(DISTINCT k2)` FROM `test`.`s1`;

mysql> explain select count(1) from s1;
+-----------------------------+
| Explain String |
+-----------------------------+
| PLAN FRAGMENT 0 |
| OUTPUT EXPRS:4: count |
| PARTITION: UNPARTITIONED |
| |
| RESULT SINK |
| |
| 2:EXCHANGE |
| |
| PLAN FRAGMENT 1 |
| OUTPUT EXPRS: |
| PARTITION: RANDOM |
| |
| STREAM DATA SINK |
| EXCHANGE ID: 02 |
| UNPARTITIONED |
| |
| 1:Project |
| | <slot 4> : count(5: 1) |
| | |
| 0:OlapScanNode |
| TABLE: test_mv1 |
| PREAGGREGATION: ON |
| partitions=1/1 |
| rollup: test_mv1 |
| tabletRatio=2/2 |
| tabletList=30937,30939 |
| cardinality=1 |
| avgRowSize=8.0 |
| MaterializedView: true |
+-----------------------------+
29 rows in set (0.00 sec)

Query will face this error:

mysql> select count(1) from s1;

ERROR 1064 (HY000): Vectorized engine does not support the operator, node_type: 0 backend [id=10001] [host=172.26.92.227]

## What I'm doing:
- Fix mv rewrite wrong plans if query only contains constant call operators 

Fixes #issue

## What type of PR is this:

- [x] 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.
- [x] 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:

- [x] 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
- [x] This is a backport pr

[mergify]

Cherry-pick of 215c164 has failed:

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

You are currently cherry-picking commit 215c16499f.
  (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/transformation/materialization/EquationRewriter.java

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	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 failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint