chore(deps): Update sqlparser to 0.56.0

[Dimchikkk]

Which issue does this PR close?

• Closes Upgrade to sqlparser 0.56.0 #16405

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[Dimchikkk]

Without this change the test fails:

#[test]
fn test_order_by_to_sql_3() {
    let statement = generate_round_trip_statement(
        GenericDialect {},
        r#"SELECT id, first_name, substr(first_name,0,5) FROM person ORDER BY id, substr(first_name,0,5)"#,
    );
    assert_snapshot!(
        statement,
        @r#"SELECT person.id, person.first_name, substr(person.first_name, 0, 5) FROM person ORDER BY person.id ASC NULLS LAST, substr(person.first_name, 0, 5) ASC NULLS LAST"#
    );
}

In the previous version substr were hitting:

            SQLExpr::Function(function) => {
                self.sql_function_to_expr(function, schema, planner_context)
            }

now it's hitting:

            SQLExpr::Substring {
                expr,
                substring_from,
                substring_for,
                special: _,
                shorthand: _,
            } => self.sql_substring_to_expr(
                expr,
                substring_from,
                substring_for,
                schema,
                planner_context,
            ),

Open for suggestions if there is a better way to handle it.

[Dimchikkk]

Not sure if the new data types should be handled here or Unsupported SQL type is fine.

[Dimchikkk]

Not sure if I should create a new set_expr_to_plan function or wrapping subquery and passing it to query_to_plan is fine.

[Dimchikkk]

(converted to draft while I'm investigating CI failures)

[Dimchikkk]

(one of the test failures is related to #1898 and would be fixed if that patch is backported to 0.56)