inline agg test in ckb

[Mryange]

What problem does this PR solve?

只用来跑ckb的。
对于sum命中不了的0.374 sec
对于count可以命中的 0.312 sec

在 #61043 中测试可以跑过流水线

MySQL [hits]> SELECT ClientIP,sum(ClientIP) AS c
    -> FROM hits
    -> GROUP BY ClientIP
    -> ORDER BY c DESC
    -> LIMIT 10;

+------------+----------------+
| ClientIP   | c              |
+------------+----------------+
| 1696638182 | 34306024040040 |
| 1740861572 | 19696107825608 |
| 1138507705 | 17963374569490 |
| 2068464272 | 15252855541728 |
| 2061209781 | 14236775957367 |
| 1990169817 | 11978832128523 |
| 1844870420 | 11823774521780 |
| 1804647842 | 11203253803136 |
| 2146977381 | 11117048878818 |
| 2128431738 | 11076358764552 |
+------------+----------------+
10 rows in set (0.374 sec)

MySQL [hits]> 
MySQL [hits]> SELECT ClientIP, COUNT(*) AS c
    -> FROM hits
    -> GROUP BY ClientIP
    -> ORDER BY c DESC
    -> LIMIT 10;
+-------------+-------+
| ClientIP    | c     |
+-------------+-------+
|   -39921974 | 47008 |
| -1698104457 | 29121 |
| -1175819552 | 25333 |
|  1696638182 | 20220 |
|  1138507705 | 15778 |
|  -927025522 | 12768 |
| -1262139876 | 11348 |
|  1740861572 | 11314 |
|  -807147100 |  9880 |
|  -631062503 |  9718 |
+-------------+-------+
10 rows in set (0.312 sec)

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?