### 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/Querier.java
} else {
                    size = limit;
                }
            }
            this.data = new AggSortingQueue(size, sortingColumns);
        }
        @Override
        public void onResponse(Page page) {
            
            if (schema == null) {
                RowSet rowSet = page.rowSet();
                if (rowSet instanceof SchemaRowSet schemaRowSet) {
                    schema = schemaRowSet.schema();
                } else {
                    onFailure(new SqlIllegalArgumentException("No schema found inside {}", rowSet.getClass()));
                    return;
                }
            }
            
            if (consumeRowSet(page.rowSet()) == false) {
                return;
            }
            Cursor cursor = page.next();
            
            if (cursor != Cursor.EMPTY) {
                
                planExecutor.nextPageInternal(cfg, cursor, this);
                
                return;
            }