[debug log](local merge) add more info in local merge sort

[Mryange]

What problem does this PR solve?

Unlike other local exchanges, local merge has a while loop. Previously, there were issues with infinite loops.

LOCAL_EXCHANGE_OPERATOR (LOCAL_MERGE_SORT): id=-4, parallel_tasks=4, _is_serial_operator=false, _channel_id: 0, _num_partitions: 4, _num_senders: 4, _num_sources: 4, _running_sink_operators: 0, _running_source_operators: 1, mem_usage: 0, data queue info: Data Queue 0: [size approx = 0, eos = false , block_supplier [still running = false, all have eof = false] ], MemTrackers: 0: 0, 1: 768, 2: 768, 3: 0, 
  DATA_STREAM_SINK_OPERATOR: id=5, _is_serial_operator=false, Sink Buffer: (_is_finishing = false, blocks in queue: 0, queue capacity: 64, queue dep: 0x7fc0cc814010), _reach_limit: false, working channels: 1
0.   this=0x7fbd6169c510, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fbd6169c710, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fbd6169c910, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fbd6169cb10, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true



operators: 
LOCAL_EXCHANGE_OPERATOR (LOCAL_MERGE_SORT): id=-4, parallel_tasks=4, _is_serial_operator=false, _channel_id: 0, _num_partitions: 4, _num_senders: 4, _num_sources: 4, _running_sink_operators: 0, _running_source_operators: 1, mem_usage: 0, data queue info: Data Queue 0: [size approx = 0, eos = false , block_supplier [still running = true, all have eof = false] ], MemTrackers: 0: 0, 1: 0, 2: 0, 3: 0, 
  DATA_STREAM_SINK_OPERATOR: id=5, _is_serial_operator=false, Sink Buffer: (_is_finishing = false, blocks in queue: 0, queue capacity: 64, queue dep: 0x7fc11a275810), _reach_limit: false, working channels: 1
0.   this=0x7fc099b94410, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fc099b94610, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fc099b94810, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true
0.   this=0x7fc099b94a10, LOCAL_MERGE_EXCHANGE_OPERATOR_DEPENDENCY: id=-4, block task = 0, ready=true, _always_ready=true

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

[Mryange]

run buildall

[doris-robot]

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?

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[Mryange]

run buildall

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[Mryange]

run p0

[Mryange]

run buildall

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[doris-robot]

TeamCity be ut coverage result:
Function Coverage: 37.92% (9886/26069)
Line Coverage: 29.12% (82598/283639)
Region Coverage: 28.26% (42459/150260)
Branch Coverage: 24.85% (21540/86696)
Coverage Report: http://coverage.selectdb-in.cc/coverage/b514de7a91e4d41370c77263d76580153268177c_b514de7a91e4d41370c77263d76580153268177c/report/index.html