Add ability to configure SQL parser dialect in SessionState

[Viicos]

Which issue does this PR close?

Fixes #23109.

Rationale for this change

What changes are included in this PR?

This is one approach that tries solving #23109, by allowing the SQL parser dialect to be configured at the SessionState level.

It's still a bit inconsistent, because it doesn't follow what is set at the config level (see issue), but I guess better than nothing?

Are these changes tested?

Yes.

Are there any user-facing changes?

No.

[adriangb]

It's still a bit inconsistent, because it doesn't follow what is set at the config level (see issue), but I guess better than nothing?

What do you mean? That it's not possible to set a custom SQL dialect from a string name, e.g. SET datafusion.sql_parser.dialect = 'custom'? If so this seems like a non-issue to me. There's plenty of dyn APIs that are not configurable from SQL, I'd consider this a pretty advanced usage of DataFusion.

What does the config return once you set a custom dialect using these APIs (SHOW datafusion.sql_parser.dialect;)?

[Viicos]

What do you mean? That it's not possible to set a custom SQL dialect from a string name, e.g. SET datafusion.sql_parser.dialect = 'custom'? If so this seems like a non-issue to me. There's plenty of dyn APIs that are not configurable from SQL, I'd consider this a pretty advanced usage of DataFusion.

Makes sense, most likely it makes sense for users using this API to make sure they set their datafusion.sql_parser.dialect config to a custom value like 'my_custom_dialect' or something.