Ensure memory is freed in SpoolingExchangeOutputBuffer

[arhimondr]

Description

Close memory context to prevent race condition when memory is reserved
in enqueuePage after output buffer destroy following the pattern used in
other output buffers

Is this change a fix, improvement, new feature, refactoring, or other?

Fix

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Core engine

How would you describe this change to a non-technical end user or system administrator?

N/A

Related issues, pull requests, and links

#13362

Documentation

(X) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(X) No release notes entries required.
( ) Release notes entries required with the following suggested text:

[sopel39]

not every memory context is closeable, see https://github.com/trinodb/trino/pull/13213/files#diff-1774b86bf4c8b2248f02693fe0b0c6acc38305a6773ca813f5957601207a8168R338.
I think we can assume that only memory context created from io.trino.memory.context.AggregatedMemoryContext#newAggregatedMemoryContext are closeable

[arhimondr]

The other output buffers close the memory context through the OutputBufferMemoryManager: https://github.com/trinodb/trino/blob/master/core/trino-main/src/main/java/io/trino/execution/buffer/OutputBufferMemoryManager.java#L199

The memory context is closeable. It is created in https://github.com/trinodb/trino/blob/master/core/trino-main/src/main/java/io/trino/operator/TaskContext.java#L157 through https://github.com/trinodb/trino/blob/master/lib/trino-memory-context/src/main/java/io/trino/memory/context/MemoryTrackingContext.java#L136