Frozen indices are deprecated which makes all the [SQL features supporting frozen indices](https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-index-frozen.html) obsolete.

This includes:

* `index_include_frozen` request parameter in the `_sql` endpoint
* `index.include.frozen` (J|O)DBC driver settings
* `SHOW TABLES INCLUDE FROZEN` queries and the `FROZEN INDEX` kind in the corresponding response
* The `FROZEN` modifier in `FROM` clauses (as in `SELECT * FROM FROZEN archive`)

`_search` raises a deprecation warning when frozen indices are being searched with `ignore_throttled=false`. SQL could do the same when the `index_include_frozen` request parameter is set or when the `FROZEN` keyword is used.

Relates to https://github.com/elastic/elasticsearch/issues/70192
x-pack/plugin/sql/src/main/java/org/elasticsearch/xpack/sql/parser/LogicalPlanBuilder.java
return plan;
    }
    private List<NamedExpression> namedValues(PivotArgsContext args) {
        if (args == null || args.isEmpty()) {
            return emptyList();
        }
        List<NamedExpression> values = new ArrayList<>();
        for (NamedValueExpressionContext value : args.namedValueExpression()) {
            Expression exp = expression(value.valueExpression());
            String alias = visitIdentifier(value.identifier());
            Source source = source(value);
            values.add(alias != null ? new Alias(source, alias, exp) : new UnresolvedAlias(source, exp));
        }
        return values;
    }
    @Override
    public LogicalPlan visitRelation(RelationContext ctx) {
        
        
        
        LogicalPlan result = plan(ctx.relationPrimary());
        for (JoinRelationContext j : ctx.joinRelation()) {
            result = doJoin(j);
        }
        return result;
    }
    private Join doJoin(JoinRelationContext ctx) {
        JoinCriteriaContext criteria = ctx.joinCriteria();
        if (criteria != null) {
            if (criteria.USING() != null) {