[Enhancement] support push down agg distinct limit (backport #55455)

[mergify]

Why I'm doing:

select distinct upper(lo_orderkey),lo_linenumber from lineorder limit 10;

	CPU	mem
baseline	30.70 sec	45.454G
patched	21ms	12.430 MB

What I'm doing:

In this patch, we support pushing the distinct limit down to the streaming agg.
The streaming agg will force a preagg pattern for the pushed limit. (Otherwise the limit may lead to undesired results, e.g., a duplicate value in the streaming section reaches the limit limit).

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 [Enhancement] support push down agg distinct limit #55455 done by Mergify.

Why I'm doing:

select distinct upper(lo_orderkey),lo_linenumber from lineorder limit 10;

	CPU	mem
baseline	30.70 sec	45.454G
patched	21ms	12.430 MB

What I'm doing:

In this patch, we support pushing the distinct limit down to the streaming agg.
The streaming agg will force a preagg pattern for the pushed limit. (Otherwise the limit may lead to undesired results, e.g., a duplicate value in the streaming section reaches the limit limit).

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 4f45265 has failed:

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

You are currently cherry-picking commit 4f452658be.
  (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/plan/PlanFragmentBuilder.java

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   be/src/exec/aggregate/agg_hash_set.h
	both modified:   be/src/exec/aggregate/agg_hash_variant.cpp
	both modified:   be/src/exec/aggregate/agg_hash_variant.h
	both modified:   be/src/exec/aggregate/aggregate_blocking_node.cpp
	both modified:   be/src/exec/pipeline/aggregate/aggregate_blocking_sink_operator.h
	both modified:   be/src/exec/pipeline/aggregate/aggregate_distinct_streaming_sink_operator.cpp
	both modified:   be/src/exec/pipeline/aggregate/aggregate_distinct_streaming_sink_operator.h
	both modified:   be/src/exec/pipeline/aggregate/spillable_aggregate_blocking_sink_operator.cpp
	both modified:   fe/fe-core/src/main/java/com/starrocks/qe/SessionVariable.java
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/sql/optimizer/rule/transformation/SplitTwoPhaseAggRule.java
	both modified:   fe/fe-core/src/test/java/com/starrocks/sql/plan/AggregateTest.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