runaway: fix the issue where COOLDOWN/SWITCH_GROUP can't be triggered

[JmPotato]

What problem does this PR solve?

Issue Number: close #60404

Problem Summary:

Run the corresponding actions in BeforeCopRequest once it's marked by IdentifyInRunawaySettings.

What changed and how does it work?

Check List

Tests

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

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix the issue where `COOLDOWN`/`SWITCH_GROUP` can't be triggered with `QUERY_LIMIT`.

[codecov]

Codecov Report

Attention: Patch coverage is 44.11765% with 19 lines in your changes missing coverage. Please review.

Project coverage is 73.5172%. Comparing base (c9b33d6) to head (4e2e28d).
Report is 524 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #60457        +/-   ##
================================================
+ Coverage   73.0908%   73.5172%   +0.4263%     
================================================
  Files          1714       1714                
  Lines        474865     474916        +51     
================================================
+ Hits         347083     349145      +2062     
+ Misses       106433     104436      -1997     
+ Partials      21349      21335        -14     

Flag	Coverage Δ
integration	42.6465% <0.0000%> (?)
unit	72.3316% <44.1176%> (+0.0295%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6553% <ø> (ø)
parser	∅ <ø> (∅)
br	47.2823% <ø> (+0.0083%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[glorv]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: glorv, nolouch

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [glorv,nolouch]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-04-10 16:47:40.558706114 +0000 UTC m=+2361354.242942210: ☑️ agreed by glorv.
• 2025-04-15 03:48:41.242955721 +0000 UTC m=+2746614.927191802: ☑️ agreed by nolouch.

[JmPotato]

/test check-dev2

[tiprow]

@JmPotato: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[JmPotato]

/test unit-test

[tiprow]

@JmPotato: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

Details

In response to this:

/test unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[JmPotato]

/cherry-pick release-8.5

[ti-chi-bot]

@JmPotato: new pull request created to branch release-8.5: #60568.
But this PR has conflicts, please resolve them!

Details

In response to this:

/cherry-pick release-8.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #62299.
But this PR has conflicts, please resolve them!