feat(scan): quick cancel query with proactive manager

[MrSanZhi]

What is changed and how it works?

When the memory exceeds a certain threshold, the crash method is used to quickly interrupt the query and push each executor to exit quickly.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B
• Test cases to be added
• No code

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

Attention: Patch coverage is 81.81818% with 16 lines in your changes are missing coverage. Please review.

Project coverage is 74.74%. Comparing base (502f6cd) to head (3cd271c).
Report is 13 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #506      +/-   ##
==========================================
- Coverage   74.75%   74.74%   -0.01%     
==========================================
  Files         558      558              
  Lines      118218   118297      +79     
==========================================
+ Hits        88369    88426      +57     
- Misses      24344    24365      +21     
- Partials     5505     5506       +1     

[xiangyu5632]

engine/column_store_reader.go:373 ,need

err = r.initReadCursor(ctx)