Describe the bug

In a cluster, these logs repeat excessively, leading to increased log costs and overwhelming other entries.

• large chunk in exchange. Should it be DEBUG?
• kinesis reader throttling. It repeats every 200 ms in the worst case. Should it be DEBUG?
• handle multiple barriers at once in now executor. Should it be DEBUG?
• It appears that the backtrace in the log is unnecessary, e.g. this. Should it be %e.as_report() instead?
• verbose foyer logs that has been fixed but need to be merged in to RW.

Error message/log

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