[Bug](cancel) fix ctrl+c can not cancel query

[BiteTheDDDDt]

What problem does this PR solve?

before

mysql>selectcount(*) from d_table;
+----------+
| count(*) |
+----------+
| 10000000 |
+----------+1 row inset (0.23 sec)
mysql>select*from d_table;
^C^C -- query aborted+---------+---------+---------+------+
| k1 | k2 | k3 | k4 |
+---------+---------+---------+------+
| 2 | 2 | 2 | a |
+---------+---------+---------+------+10000000 rows inset (1 min 6.28 sec)

after:

mysql>select*from d_table;
^C^C -- query aborted
ERROR 1105 (HY000): errCode =2, detailMessage = cancel query by user from127.0.0.1:53598

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

[BiteTheDDDDt]

run buildall

[Thearas]

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?

[BiteTheDDDDt]

run buildall

[BiteTheDDDDt]

run buildall

[hello-stephen]

BE Regression && UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	79.32% (20833/26264)
Line Coverage	72.50% (214326/295627)
Region Coverage	70.67% (126057/178381)
Branch Coverage	64.45% (65339/101386)

[BiteTheDDDDt]

run buildall

[hello-stephen]

BE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	55.82% (14903/26698)
Line Coverage	44.61% (131937/295750)
Region Coverage	43.66% (66331/151920)
Branch Coverage	38.27% (33983/88798)

[BiteTheDDDDt]

run buildall

[BiteTheDDDDt]

run buildall

[BiteTheDDDDt]

run buildall

[hello-stephen]

BE Regression && UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	79.25% (20813/26264)
Line Coverage	72.46% (214270/295689)
Region Coverage	70.65% (126065/178432)
Branch Coverage	64.38% (65295/101414)

[BiteTheDDDDt]

run buildall

[hello-stephen]

BE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	55.87% (14883/26641)
Line Coverage	44.65% (131877/295362)
Region Coverage	43.76% (66396/151731)
Branch Coverage	38.36% (34020/88690)

[BiteTheDDDDt]

This problem has been fixed in #50791, so close the PR