Fix clickhouse-data: make NonBlockingPipedOutputStream.close() idempotent

[jjj-n]

Summary

Make NonBlockingPipedOutputStream.close() atomically claim the close path before flushing its pending buffer. Previously, two concurrent callers could both pass the volatile closed check, mutate and enqueue the same ByteBuffer, enqueue the end-of-stream marker twice, and run the post-close action twice. If the second caller changed the already-queued buffer's limit to zero, the reader observed a clean EOF and silently lost the pending payload.

Exactly one caller now flushes pending data, enqueues the end-of-stream marker, and runs the post-close action. Concurrent or repeated close() calls return immediately. The implementation follows the AtomicBoolean pattern already used by BlockingPipedOutputStream, without holding the instance monitor across the close path or a potentially blocking post-close action.

Closes #3057

Compatibility

There is no public API, configuration, default, output-format, serialization, or exception-type change. A single close() keeps its existing behavior. Only a redundant concurrent close changes from racing with the first caller to returning without touching the buffer or queue. docs/features.md is not affected because this change is confined to clickhouse-data.

Test

Added testConcurrentClose, which holds the first close at the pending-buffer offer, invokes a second close concurrently, and verifies that the second caller returns without waiting, the post-close action runs exactly once, the pending bytes are preserved, and the reader sees EOF afterward.

• Before the production fix, the new test failed with expected [1] but found [2] for the post-close action count.
• mvn -pl clickhouse-data -Dtest=NonBlockingPipedOutputStreamTest test: 6 tests passed.
• mvn -pl clickhouse-data test: 1,668 tests passed; 113 skipped by the existing suite configuration.
• mvn -Dj8 -pl clickhouse-data -Dtest=NonBlockingPipedOutputStreamTest test: Java 8 source/target compilation succeeded and 6 tests passed.

Checklist

• Closes NonBlockingPipedOutputStream.close() is not idempotent: concurrent close silently drops the pending buffer #3057
• A focused unit test covering concurrent close was added
• A human-readable description was added to CHANGELOG.md

[CLAassistant]

All committers have signed the CLA.

[chernser]

@jjj-n

These tests are failing (I've took from your fork)

[ERROR] Failures: 
[ERROR]   StatementTest.testConnectionExhaustion:653 Exception expected
[ERROR]   StatementTest.testUpdateQueryWithResultSet:1333 Connection seems closed when should not expected [true] but found [false]
[INFO]

Would you please fix? Thanks!

[chernser]

please pull latest from main and check this tests failing

[ERROR] Failures: 
[ERROR]   StatementTest.testConnectionExhaustion:653 Exception expected
[ERROR]   StatementTest.testUpdateQueryWithResultSet:1333 Connection seems closed when should not expected [true] but found [false]
[INFO]

[chernser]

@jjj-n I see the problem in expired ssl certificate. I'll approve and merge.