### Description

Only "search hits" based queries (no aggregations) provide a consistent view on the data when paginating through the result set. With point-in-time, it is possible to support transactional semantics for aggregation queries as well.

This issue is somewhat blocked by https://github.com/elastic/elasticsearch/issues/75528 because a PIT can not immediately be closed if the aggregation result set contains less than `fetch_size` records. This could cause some increased resource utilization due to open PITs. Especially if the client does not close the SQL cursor.
x-pack/plugin/sql/src/main/java/org/elasticsearch/xpack/sql/execution/search/CompositeAggCursor.java
public void writeTo(StreamOutput out) throws IOException {
        out.writeStringArray(indices);
        nextQuery.writeTo(out);
        out.writeVInt(limit);
        out.writeNamedWriteableList(extractors);
        out.writeByteArray(mask.toByteArray());
        out.writeBoolean(includeFrozen);
    }
    @Override
    public String getWriteableName() {
        return NAME;
    }
    String[] indices() {
        return indices;
    }
    SearchSourceBuilder next() {
        return nextQuery;
    }
    BitSet mask() {
        return mask;
    }
    List<BucketExtractor> extractors() {
        return extractors;
    }
    int limit() {
        return limit;
    }
    boolean includeFrozen() {
        return includeFrozen;
    }