[Enhancement] add more profile and metrics to measure runtime bloom filter size (backport #46360)

[mergify]

Why I'm doing:

What I'm doing:

Major changes:

1. add new metrics to query profile to observe the memory occupied by partial runtime bloom filter.
2. add new be system metrics to observe the number of rf events in the queue and the bloom filter memory consumption in the queue.

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

---

This is an automatic backport of pull request #46360 done by [Mergify](https://mergify.com). ## Why I'm doing:

What I'm doing:

Major changes:

1. add new metrics to query profile to observe the memory occupied by partial runtime bloom filter.
2. add new be system metrics to observe the number of rf events in the queue and the bloom filter memory consumption in the queue.

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 16ec9c1 has failed:

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

You are currently cherry-picking commit 16ec9c16fe.
  (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:   be/src/exec/hash_joiner.cpp
	modified:   be/src/exec/hash_joiner.h
	modified:   be/src/exprs/runtime_filter.h
	modified:   be/src/util/system_metrics.cpp
	modified:   be/src/util/system_metrics.h

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   be/src/exec/pipeline/hashjoin/hash_join_build_operator.cpp
	both modified:   be/src/runtime/runtime_filter_worker.cpp
	both modified:   be/src/runtime/runtime_filter_worker.h

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