feat(batch): support spill hash agg for the batch query

[chenzl25]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

• Related RFC: RFC: Spill Hash Aggregation rfcs#89
• Tracking issue Tracking: batch query memory control and spill #16615
• Support spill hash agg for the batch query.
• When HashAggExecutor told memory is insufficient, AggSpillManager will start to partition the hash table and spill to disk. After spilling the hash table, AggSpillManager will consume all chunks from the input executor, partition and spill to disk with the same hash function as the hash table spilling. Finally, we would get e.g. 20 partitions. Each partition should contain a portion of the original hash table and input data. A sub HashAggExecutor would be used to consume each partition one by one. If memory is still not enough in the sub HashAggExecutor, it will partition its hash table and input recursively.
• SpillOp is used to manage the spill directory of the spilling executor and it will drop the directory with a RAII style.
• An environment variable RW_BATCH_SPILL_DIR would be used to configure the path to spill, by default /tmp/.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

• Support spill hash agg for the batch query.

[st1page]

Maybe we need to test the case that the directory of the FS is full? And how to GC the spilled data 🤔

[chenzl25]

Maybe we need to test the case that the directory of the FS is full? And how to GC the spilled data 🤔

If the disk is full, the IO should throw an error. When the query is aborted, it will release its disk occupation.

[st1page]

Maybe we need to test the case that the directory of the FS is full? And how to GC the spilled data 🤔

If the disk is full, the IO should throw an error. When the query is aborted, it will release its disk occupation.

Yes, And maybe we need to clean the spilled file somewhere when the batch task is dropped

[fuyufjh]

Overall LGTM