Truly kill a query when it exceeds max excution time even if mysql client gets stuck

[gengliqi]

Enhancement

In the current implementation, the kill operation will take effect only after calling next function.
However, if a MySQL client doesn't receive data for a long time, the next function wasn't called for a long time either.
This case can lead to many resources(i.e. goroutine, memory) can not be released.
Also, many logs like below will be outputted each 100ms, which is very annoying.

In order to improve robustness, we need to change the kill process to release resources as many as possible.

[wuhuizuo]

Can we close it since #44675 was solved?

[gengliqi]

close due to #52882