fix(streaming): don't recycle in-flight pooled buffers mid-batch
Problem
Fixes #10263.
Pooled stream caches (EventHub, Memory, Generator) can silently corrupt message payloads, which later surfaces as an ArgumentOutOfRangeException in SegmentBuilder.ReadNextString.
ChronologicalEvictionStrategy.OnBlockAllocated eagerly freed the previous pooled buffer whenever the cache reported empty (PurgeObservable.IsEmpty). That was safe when the strategy was written, but callers now encode an entire batch into pooled buffers before committing it to the cache. During that encode IsEmpty stays true, so the buffer being freed can still hold in-flight, uncommitted segments for the current batch. The freed buffer is returned to the (LIFO) object pool, and the very next allocation in the same batch pops it straight back and overwrites the earlier segments from offset 0 — corrupting those messages. The three pooled caches all share this eviction strategy, so all of them are affected, not just EventHub.
Solution
Remove the eager-free branch in OnBlockAllocated. In-use buffers are already reclaimed correctly at purge time by FreePurgedBuffers, which only releases buffers once their segments are no longer referenced by committed messages.
Removing the eager-free would, on its own, expose a pre-existing buffer leak: for a message too large to ever fit in a pooled buffer, the eager-free was the only thing that reclaimed the freshly allocated (and never-committed) block. To close that, the EventHub, Memory and Generator caches now dispose the freshly allocated block back to the pool and throw before registering it with the eviction strategy, so repeated oversized (poison) messages reuse a single block instead of growing the retained set without bound.
Adds regression tests for multi-buffer batch payload integrity from an empty cache and for the oversized-message no-leak behavior. Both fail without the fix and pass with it.