expensivequery: fix the issue that max_exec_time hint doesn't work if it exceeds the expensive-threshold (#17359)

[sre-bot]

cherry-pick #17359 to release-3.0

---

What problem does this PR solve?

Issue Number: close #17355, #17393

Problem Summary:

1. Minimal reproduce step (Required)

set @@max_execution_time=60000;
select sleep(70);

2. What did you expect to see? (Required)

mysql> select sleep(70);
+-----------+
| sleep(70) |
+-----------+
| 1 |
+-----------+
1 row in set (1 min )

3. What did you see instead (Required)

mysql> select sleep(70);
+-----------+
| sleep(70) |
+-----------+
|         0 |
+-----------+
1 row in set (1 min 10.00 sec)

What is changed and how it works?

What's Changed:
repair max_execution_time sometimes fails.
How it Works:
The MaxExecutionTime and ExceedExpensiveTimeThresh check logic separately.

Related changes

• Need to cherry-pick to the release branch
  cherry-pick: V3.0,V3.1,V4.0

Check List

Tests

• Unit test

Release note

• Fix the issue that the max_execution_time sometimes fails.

[sre-bot]

/run-all-tests

[qw4990]

LGTM

[XuHuaiyu]

LGTM

[tiancaiamao]

/run-all-tests

[bb7133]

/merge

[sre-bot]

/run-all-tests

[sre-bot]

@sre-bot merge failed.

[bb7133]

/run-mybatis-test