### 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/SearchHitCursor.java
SearchSourceBuilder next() {
        return nextQuery;
    }
    BitSet mask() {
        return mask;
    }
    List<HitExtractor> extractors() {
        return extractors;
    }
    int limit() {
        return limit;
    }
    boolean includeFrozen() {
        return includeFrozen;
    }
    @Override
    public void nextPage(SqlConfiguration cfg, Client client, ActionListener<Page> listener) {
        if (log.isTraceEnabled()) {
            log.trace("About to execute search hit query {}", StringUtils.toString(nextQuery));
        }
        SearchRequest request = prepareRequest(nextQuery, cfg.requestTimeout(), includeFrozen);
        client.search(
            request,
            ActionListener.wrap(
                (SearchResponse response) -> handle(client, response, request.source(), makeRowSet(response), listener, includeFrozen),
                listener::onFailure
            )
        );
    }
    private Supplier<SearchHitRowSet> makeRowSet(SearchResponse response) {