[BugFix] fix agg in order by not being analyzed correctly

[packy92]

Fixes #issue
For sql like

select min(v1) v1 from t0 group by v3 order by round(count(v2) / min(v1)), min(v1), abs(v1);

The statement had been transformed to a wrong plan fragment like:

LogicalProjectOperator {projection=[3: v3, 5: count, 6: min, min(1: v1)]}
            ->  LogicalAggregation {type=GLOBAL ,aggregations={4: min=min(1: v1), 5: count=count(2: v2), 6: min=min(1: v1)} ,groupKeys=[3: v3]}

This reason is the scope for analyzing order by is combined querySource scope and output scope. For the order by elements in the sql, its scope is like output scope: v1(tblName null), source scope: v1(tblName t0), v2(tblName t0), v3(tblName t0). When analyze min(v1), the v1 matched with v1(tblName null) firstly, while it should be v1(tblName t0). Even the old code would analyze the aggregations using source scope in the later step, the fisrt analyzed process has put the slotRef in a map. The second analyzed process may change the slotRef already in the map, leading to unexpect behavior when get obejct from the map.
So, the better way is to distinguish the aggregation func from the normal func in the analyze orderby stage, and use the corresponding scope to process them respectively.

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

Bugfix cherry-pick branch check:

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

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

0.0% Coverage
0.0% Duplication

The version of Java (11.0.20.1) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

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

[wanpengfei-git]

[BE Incremental Coverage Report]

😍 pass : 0 / 0 (0%)

[wanpengfei-git]

[FE Incremental Coverage Report]

😍 pass : 10 / 10 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/sql/analyzer/SelectAnalyzer.java	5	5	100.00%	[]
🔵	com/starrocks/sql/analyzer/AggregationAnalyzer.java	1	1	100.00%	[]
🔵	com/starrocks/sql/analyzer/ExpressionAnalyzer.java	4	4	100.00%	[]

[wanpengfei-git]

@Mergifyio backport branch-3.1

[wanpengfei-git]

@Mergifyio backport branch-3.0

[mergify]

backport branch-3.1

✅ Backports have been created

• #30237 [BugFix] fix agg in order by not being analyzed correctly (backport #30108) has been created for branch branch-3.1

[mergify]

backport branch-3.0

✅ Backports have been created

• #30238 [BugFix] fix agg in order by not being analyzed correctly (backport #30108) has been created for branch branch-3.0 but encountered conflicts