### 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
final Client client;
        final SqlConfiguration cfg;
        final Schema schema;
        BaseActionListener(ActionListener<Page> listener, Client client, SqlConfiguration cfg, List<Attribute> output) {
            super(listener);
            this.client = client;
            this.cfg = cfg;
            this.schema = Rows.schema(output);
        }
        @Override
        public void onResponse(final SearchResponse response) {
            handleResponse(response, delegate);
        }
        protected abstract void handleResponse(SearchResponse response, ActionListener<Page> listener);
    }
    @SuppressWarnings("rawtypes")
    static class AggSortingQueue extends PriorityQueue<Tuple<List<?>, Integer>> {
        private List<Tuple<Integer, Comparator>> sortingColumns;
        AggSortingQueue(int maxSize, List<Tuple<Integer, Comparator>> sortingColumns) {
            super(maxSize);
            this.sortingColumns = sortingColumns;
        }
        /**
         * Compare row based on the received attribute sort
         * <ul>