fix: handle Annotated nodes in lineage column resolution

[eitsupi]

Summary

• Fix get_alias_or_name() to unwrap Annotated expression nodes, which are produced when SQL comments appear between SELECT and the first column
• Without this fix, lineage tracing fails with "Cannot find column" for queries like:

  WITH t AS (SELECT 1 AS a)
  SELECT
    -- comment
    a FROM t

• This pattern is common in dbt compiled SQL where Jinja templates insert section comments

Details

When the parser encounters a comment before a SELECT expression, it wraps the expression in an Annotated node to preserve the comment. The get_alias_or_name() function in the lineage module only matched Alias, Column, Identifier, and Star variants — it did not handle Annotated, returning None and causing find_select_expr() to fail.

The fix adds a single recursive arm for Expression::Annotated(a) => get_alias_or_name(&a.this), consistent with how find_column_refs_in_expr already handles Annotated nodes elsewhere in the same file.

Test plan

• Add test: line comment before first column in CTE query
• Add test: block comment before first column
• Add test: comment before first column with multiple columns (second column unaffected)
• Add test: comment before aliased column
• Add test (ignored): ported sqlglot test_node_name_doesnt_contain_comment (requires derived table star expansion, separate issue)
• All 942 existing tests pass

🤖 Generated with Claude Code