[Feature] LazyMemorySegmentPool use BlockingQueue instead of using list with lock

[wuchong]

^{Originally posted by swuferhong November 27, 2024}
Currently, in LazyMemorySegmentPool, we use a List with a lock to manage cachePages. This approach requires the use of locks and manual writing await logic, which is not as efficient as using a BlockingQueue. Moreover, replacing it with a BlockingQueue would not introduce any potential correctness issues.

[wuchong]

LazyMemorySegmentPool has been refactored in commit d0b466f. It introduced a List<MemorySegment> allocatePages(int required) methods to allocate a batch of pages, but BlockingQueue doesn't provide this API (thread-safe). Besides, the performance and design of current implementation is similar to ArrayBlockingQueue, so it is not necessary to replace using BlockingQueue. So close this issue as invalid.