Metabase cannot trace Native SQL dependencies in Data Studio Dependency Graph

**What problem will this feature request solve?**
Customer's want to use Data Studio to manage complex dependency trees/computational graphs, but they can only do so to the level of GUI Questions since Metabase does not parse SQL

**Describe the solution you'd like.**
- Enable Metabase users to see SQL dependencies in the dependency graph in Data Studio and other places where dependencies are shown

Alternative stop-gap that would be beneficial is partial SQL parsing (i.e. attempt parsing, and only show results if successful and validated results, and just flag unparseable SQL Questions as unparseable)

**How does this feature request impact you?**
- extremely valuable for customers who want to prioritize Metabase and Data Studio for their ETL/ELT/Data Pipelines/computational graph management

**Additional information**
- Related to (all depend on effective SQL parsing):
- https://github.com/metabase/metabase/issues/10525
- https://github.com/metabase/metabase/issues/51326
- https://github.com/metabase/metabase/issues/11173

Start by reviewing related issues #10525, #51326, and #11173 to understand the existing SQL-parsing context. Define the scope for tracing SQL dependencies in Data Studio and other dependency views, including how unparseable queries should be represented. Done means validated SQL dependencies appear in the dependency graph and unparseable queries are handled explicitly.

Written by the indexing model from the issue text.