bug(sink): panic on "should not receive any data after pause"

[zwang28]

Describe the bug

The only compute node panicked on panicked at src/stream/src/executor/sink.rs:277:21:\nShould not receive any data after pause.

There're sinks in the cluster. The user was creating multiple sink into table at the time.

https://risingwave-labs.slack.com/archives/C034TRPKN1F/p1730175390802129

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

v2.0.2

Additional context

No response

[zwang28]

I believe the root cause is hash agg can emit data chunk on window close on receiving a barrier, even when the stream graph is already paused. I've confirmed that the cluster experiencing the panic includes a hash aggregation with an emit on window close.
e.g. [pause, configchange, resume]

Would you PTAL at accommodating hash agg emit to pause/resume barrier? Thanks. @stdrc