[Caideyipi]

Description

Thrift client pools can retain RPC buffers sized for earlier large frames. Although idle clients already have a one-minute eviction threshold, Commons Pool checks only three objects per eviction run by default. Large pools can therefore retain expired connections and their buffers for much longer, leaving the server unable to allocate buffers for new connections.

This change makes each eviction run check every idle client across the pool and runs the sweep every 30 seconds. The existing one-minute idle threshold remains in place. Eviction closes the pooled transport and releases its read, write, and compression buffers; active clients are unaffected.

Validation

• Added regression tests showing one eviction run removes all expired clients across multiple pool keys, preserves active and unexpired clients, and allows expired buffers to be reused.
• Added real-socket tests with and without Snappy compression. After pool eviction, the server releases the closed connection's buffers and accepts a replacement connection.
• mvn test -pl iotdb-core/node-commons -am -Dtest=ClientPoolIdleEvictionTest,ClientManagerTest,AutoResizingBufferTest -Dsurefire.failIfNoSpecifiedTests=false: passed.
• mvn test-compile -DskipTests: passed.
• mvn test-compile -DskipTests -P with-zh-locale: passed.