[Refactor] Remove column pool

[trueeyu]

Why I'm doing:

ColumnPool is designed to address performance issues caused by frequent cross thread memory alloc/free.

Tcmalloc has a CentrlHeap, which results in high lock contention overhead. Currently it has been already been replaced by Jemalloc, which is now an independent arena and no longer has this issue. In version 3.2, ColumnPool` has been disabled by default, and there have been no performance issues in performance testing or user production environments.

So in main branch, it can be safely removed.

What I'm doing:

Remove column pool

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

[trueeyu]

@Mergifyio rebase main

[mergify]

rebase main

☑️ Nothing to do

• -conflict [📌 rebase requirement]
• -closed [📌 rebase requirement]
• queue-position = -1 [📌 rebase requirement]
• any of:
  • #commits > 1 [📌 rebase requirement]
  • #commits-behind > 0 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[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]

❌ fail : 14 / 22 (63.64%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/connector/lake_connector.cpp	0	1	00.00%	[136]
🔵	be/src/exec/olap_scan_node.cpp	0	4	00.00%	[211, 271, 274, 732]
🔵	be/src/common/daemon.cpp	0	3	00.00%	[176, 177, 178]
🔵	be/src/storage/chunk_helper.cpp	13	13	100.00%	[]
🔵	be/src/exec/pipeline/scan/olap_chunk_source.cpp	1	1	100.00%	[]