Bug: Frontend hangs and can't accept new connection

[chenzl25]

Describe the bug

PR #15758 could cause the following query to run a very long time(e.g. 10s).
During the major time of 10s, the execution has no await point.

select true and true and true and true and true and true and true and true and true and true and true and true and true  and true  and true  and true  and true and true and true and true and true and true and true;

During the above SQL execution period, the frontend node fails to accept a new connection which is unexpected, because we use a multi-thread tokio run time. I suspected that the tokio runtime fails to steal work from one thread to another in this case, because after using an additional runtime to run listener.accept, the new connection could be accepted timely.

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[BugenZhao]

Could be related: #9019