test(e2e): add accurate mode test for CTE with VALUES clause

Tests CTE using VALUES clause with column aliasing to verify
accurate analyzer handles inline table expressions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: kyleconroy

internal/endtoend/testdata/accurate_cte_values/postgresql/stdlib/exec.json

@@ -0,0 +1,3 @@
+{
+  "contexts": ["managed-db"]
+}

internal/endtoend/testdata/accurate_cte_values/postgresql/stdlib/go/db.go

@@ -0,0 +1,7 @@
+-- name: GetPendingSaleStatuses :many
+WITH w_pending_sale_status as (
+    select * from
+    (values ('SAVED'), ('IDLE'), ('IN PROGRESS'), ('HELD'))
+    as pending_sale_status(status)
+)
+SELECT status FROM w_pending_sale_status;

internal/endtoend/testdata/accurate_cte_values/postgresql/stdlib/go/models.go

@@ -0,0 +1 @@
+-- Empty schema - CTE uses VALUES clause only

internal/endtoend/testdata/accurate_cte_values/postgresql/stdlib/go/query.sql.go

@@ -0,0 +1,13 @@
+version: "2"
+sql:
+  - engine: "postgresql"
+    queries: "query.sql"
+    schema: "schema.sql"
+    database:
+      uri: "postgresql://postgres:mysecretpassword@localhost:5432/postgres"
+    gen:
+      go:
+        package: "querytest"
+        out: "go"
+    analyzer:
+      accurate: true