[enhancement](aggregate-function) enhance aggregate funtion collect and add group_array aliases

[Hastyshell]

Proposed changes

Issue Number: close #13982

Problem summary

Enhance aggregate function collect_set and collect_list to support optional max_size param, which enables to limit the number of elements in result array.

Checklist(Required)

1. Does it affect the original behavior:
   • Yes
   • No
   • I don't know
2. Has unit tests been added:
   • Yes
   • No
   • No Need
3. Has document been added or modified:
   • Yes
   • No
   • No Need
4. Does it need to update dependencies:
   • Yes
   • No
5. Are there any changes that cannot be rolled back:
   • Yes (If Yes, please explain WHY)
   • No

Further comments

Regression tests will be added soon.

If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[hello-stephen]

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.3 seconds
stream load tsv: 476 seconds loaded 74807831229 Bytes, about 149 MB/s
stream load json: 40 seconds loaded 2358488459 Bytes, about 56 MB/s
stream load orc: 69 seconds loaded 1101869774 Bytes, about 15 MB/s
stream load parquet: 28 seconds loaded 861443392 Bytes, about 29 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230222142950_clickbench_pr_101952.html

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy made some suggestions

[Hastyshell]

run buildall

[Hastyshell]

run p0

[Hastyshell]

run p1

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[Yukang-Lian]

LGTM

[morningman]

LGTM

[BiteTheDDDDt]

Hi, Does the case in this pr need to add some order by to ensure that the results are always consistent?
I'm running into something that looks like it's sorting related.

2023-02-28 16:58:32.363 ERROR [suite-thread-3] (ScriptContext.groovy:121) - Run test_aggregate_collect in /doris/regression-test/suites/query_p0/sql_functions/aggregate_functions/test_aggregate_collect.groovy failed
java.lang.IllegalStateException: Check tag 'select' failed:
Check tag 'select' failed, line 1, CHAR result mismatch.
Expect cell is: [1555555555, 3555555555, 9555555555, 255555555, 55555555555]
But real is: [1555555555, 9555555555, 3555555555, 255555555, 55555555555]

[Hastyshell]

Hi, Does the case in this pr need to add some order by to ensure that the results are always consistent? I'm running into something that looks like it's sorting related.

2023-02-28 16:58:32.363 ERROR [suite-thread-3] (ScriptContext.groovy:121) - Run test_aggregate_collect in /doris/regression-test/suites/query_p0/sql_functions/aggregate_functions/test_aggregate_collect.groovy failed
java.lang.IllegalStateException: Check tag 'select' failed:
Check tag 'select' failed, line 1, CHAR result mismatch.
Expect cell is: [1555555555, 3555555555, 9555555555, 255555555, 55555555555]
But real is: [1555555555, 9555555555, 3555555555, 255555555, 55555555555]

It seems so, I will add order_by to ensure the stability.