Databricks: support INSERT BY NAME

[finchxxia]

Summary

This PR adds support for Databricks INSERT ... BY NAME syntax.

• Adds a by_name field to the Insert AST node.
• Parses BY NAME for the Databricks and Generic dialects.
• Preserves BY NAME when formatting the AST back to SQL.
• Adds test coverage for INSERT INTO ... BY NAME with both SELECT and WITH queries.
• Updates existing Insert AST construction sites with the default by_name: false.

Examples

INSERT INTO target BY NAME
SELECT 1 AS a;

INSERT INTO TABLE target BY NAME
WITH source AS (
    SELECT 1 AS event_data_id
)
SELECT event_data_id FROM source;

Testing

cargo test --test sqlparser_databricks test_databricks_insert_by_name
Relevant PostgreSQL INSERT regression tests

[iffyio]

unless the syntax conflicts with other dialects (doesn't seem to be the case?) I think we can skip the dialect method and let the parser be permissive?

[iffyio]

Suggested change

	by_name = columns.is_empty()
	&& self.dialect.supports_insert_by_name()
	by_name = by_name.is_none()
	&& self.dialect.supports_insert_by_name()

I think we can drop the columns check? its not clear why it would be needed at this layer, if the implication is something semantic then that can be left up to the consumer to validate. Relatedly, I assume we need to only set the name if we don't already have one (can we cover that scenario in the tests)?

[finchxxia]

Hi @iffyio , I have committed some changes as per your suggestions. Could you plz take a look again?

[iffyio]

oh this pattern looks a bit odd, would it make more sense to do the following?

let mut by_name = self.peek_keywords(&[BY, NAME]);
let table_alias = if ... // unchanged

// ...
let partitioned = self.parse_insert_partition()?;
by_name = by_name || self.parse_keywords(&[Keyword::BY, Keyword::NAME]);

[iffyio]

maybe we can also add some scenarios with table options that cover around the new option to ensure that parsing BY NAME isn't conflicting with other features that show up around it

[iffyio]

we can remove the AST assertion and rely on verified_stmt only for these, (AST is already covered in common)