[CELEBORN-2428] Fix TierWriter buffer accounting when CompositeByteBuf insertion fails

[Kalvin2077]

What changes were proposed in this pull request?

Fix TierWriter buffer accounting and reference-count handling when CompositeByteBuf.addComponent fails before insertion or during consolidation. Add regression tests and include the shuffle key in write-error logs.

Why are the changes needed?

addComponent can fail before or after taking ownership of the buffer. Treating both cases identically can cause incorrect storage counters or buffer reference-count leaks.

Does this PR resolve a correctness bug?

• Yes

Does this PR introduce any user-facing change?

• Yes

How was this patch tested?

• Added tests for pre-insertion OOM, capacity overflow, and post-insertion consolidation OOM.
• Ran TierWriterSuite: 11 tests passed.
• Ran ./build/mvn spotless:check -pl worker.

[Kalvin2077]

@zaynt4606 @RexXiong @SteNicholas
PING

[yew1eb]

@Kalvin2077 Overall LGTM. Minor note: in Netty 4.2.10+ addComponent0 already does if (!added) buf.release() on pre-insertion failure, so the main issue here is the storeage-counter inflation rather than a ref-count leak.
By the way, the correctness label should be removed.