This update improves the SQLMesh's ability to track variable dependencies for dbt models by adding a limited support for variable names that can't be determined statically.

If static analysis determines that the value of the first argument to the {{ var() }} macro call cannot be resolved, the Jinja string(s) will be rendered using a stub adapter implementation along with a {{ var() }} macro override that captures the variable names passed into the macro during rendering.

This approach is far from bulletproof, as rendering with the stub adapter may (and likely will) result in traversing code branches different from those that would be taken with the runtime adapter. At the same time, this approach is consistent with how dbt-core itself collects ref and source dependencies.

UPD: After further deliberation, we decided to unconditionally include ALL variables associated with a package if dynamic variable names are detected. This is due to the high risk of not capturing the correct variables during rendering, which could lead to incorrect runtime behavior in cases where dbt would have worked as expected.