fix: Use clickhouse sqlglot dialect for YDB

[vgvoleg]

SUMMARY

Superset uses sqlglot to parse queries. It is not obvious in what cases it performs parsing and in what cases it doesnt, but we see an error where we are not able to use backticks and slashes in SQL Lab while creating datasets.
For example, query like

SELECT * FROM `prefix/some_name`

will fail because no sqlglot dialect is defined for YDB.

To have an ability to use db's with slashes we can use clickhouse's sqlglot dialect until we make our own.

Fixes #31322

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue: Unable to use DB names with prefixes for YDB #31322
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.81%. Comparing base (76d897e) to head (f670386).
Report is 1145 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #31323       +/-   ##
===========================================
+ Coverage   60.48%   83.81%   +23.32%     
===========================================
  Files        1931      537     -1394     
  Lines       76236    38991    -37245     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    32680    -13434     
+ Misses      28017     6311    -21706     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	48.79% <ø> (-0.38%)	⬇️
javascript	?
mysql	76.54% <ø> (?)
postgres	76.60% <ø> (?)
presto	53.28% <ø> (-0.53%)	⬇️
python	83.81% <ø> (+20.32%)	⬆️
sqlite	76.06% <ø> (?)
unit	60.91% <ø> (+3.28%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[michael-s-molina]

@vgvoleg There's also the SQLGLOT_DIALECTS_EXTENSIONS option if this is a temporary fix.

[mistercrunch]

LGTM, but would be nice for ydb to create is own dialect, even if it's just importing the clickhouse one and overriding nothing at first, and allowing for a place if/where it may diverge

[vgvoleg]

LGTM, but would be nice for ydb to create is own dialect, even if it's just importing the clickhouse one and overriding nothing at first, and allowing for a place if/where it may diverge

as I see it will be not easy to use new sqlglot version

superset/pyproject.toml

Line 96 in 48864ce

"sqlglot>=25.24.0,<25.25.0",