This is an automated cherry-pick of #9335

What problem does this PR solve?

Issue Number: close #9334

Problem Summary:

In StorageDisaggregated, the call chain buildReadTaskForWriteNode => buildReadTaskForWriteNodeTable => buildRNReadSegmentTask will create a DynamicThreadManager in each functions.

The total number of threads used in StorageDisaggregated is about request_count * batch_cop_tasks.size() * resp.tables().size() * table.segments().size().

What is changed and how it works?

Use IOThreadPool to replace DynamicThreadManager.

If the number of tasks is greater than the number of threads, DynamicThreadManager will create new threads to handle these tasks, while IOThreadPool will make these tasks queue up.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Reduce the number of threads created for handling disaggregated requests

减少处理存算分离请求创建的线程数