[Enhancement] count memory usage of approx_top_k&percentile_cont agg state

[silverbullet233]

Why I'm doing:

What I'm doing:

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

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 20 / 20 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/exprs/agg/percentile_cont.h	6	6	100.00%	[]
🔵	be/src/exec/analytor.cpp	10	10	100.00%	[]
🔵	be/src/exec/aggregator.cpp	4	4	100.00%	[]

[stdpain]

_get_window_function_result will assign result for each rows.

// DO NOT put timer here because this function will be used frequently,
    // timer will cause a sharp drop in performance.

Will this cause a performance regression?

[silverbullet233]

_get_window_function_result will assign result for each rows.

// DO NOT put timer here because this function will be used frequently,
    // timer will cause a sharp drop in performance.

Will this cause a performance regression?

No, in analytor, we just use MemHookAllocator, the logic is the same as before. there is no new timer introduced

[stdpain]

since #49206 support count the memory usage from delta.
Can we consider just counting delta so that we don't need to care about how the specific function is implemented. No additional extensions would be needed either.