refactor: use `{path, type, integer}` for start_bindings instead of just integers to avoid shadowing

In specific cases, an SQL query can reference the wrong table because the bindings are shadowed by a join/subquery. Using a more specific identifier for the binding should avoid shadowing.

No file or test is named. Start by locating start_bindings in the SQL data-layer code and trace a query where a join or subquery shadows a binding; done means the binding uses the more specific identifier and resolves the intended table, with a regression test covering the case.

Written by the indexing model from the issue text.