### 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/qa/server/src/main/java/org/elasticsearch/xpack/sql/qa/rest/RestSqlTestCase.java
containsString(": Queries with JOIN are not yet supported")
        );
        
        expectBadRequest(
            () -> runSql(randomMode(), "SELECT * FROM " + indexPattern("test") + " JOIN test"),
            containsString(": Queries with JOIN are not yet supported")
        );
        
        expectBadRequest(
            () -> runSql(
                randomMode(),
                "WITH evil AS (SELECT * FROM " + indexPattern("foo") + ") SELECT * FROM " + indexPattern("test") + " JOIN evil"
            ),
            containsString(": Queries with JOIN are not yet supported")
        );
    }
    public void testSelectGroupByAllFails() throws Exception {
        index("{\"foo\":1}", "{\"foo\":2}");
        expectBadRequest(
            () -> runSql(randomMode(), "SELECT foo FROM " + indexPattern("test") + " GROUP BY ALL foo"),
            containsString(": GROUP BY ALL is not supported")
        );
    }
    @Override
    public void testSelectInvalidSql() {
        String mode = randomFrom("jdbc", "plain");
        expectBadRequest(() -> runSql(mode, "SELECT * FRO"), containsString("1:8: Cannot determine columns for [*]"));
    }
    @Override
    public void testSelectFromMissingIndex() {