fix: redirect catalog-qualified information_schema to compat views (#383)

Queries like `ducklake.information_schema.columns` were bypassing the
compat view redirect because the transform skipped references with
an explicit `ducklake` catalog prefix. This caused failures for tools
that qualify information_schema queries with the catalog name.

The compat views use unqualified `information_schema` internally, which
resolves to the default catalog at query time, so redirecting
catalog-qualified references does not cause recursion.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: EDsCODE

transpiler/transform/information_schema.go

@@ -61,11 +61,12 @@ func (t *InformationSchemaTransform) walkAndTransform(node *pg_query.Node, chang
 	switch n := node.Node.(type) {
 	case *pg_query.Node_RangeVar:
 		// Table references: information_schema.columns -> memory.main.information_schema_columns_compat
-		// Views are created in the memory.main schema so they're always accessible regardless of default catalog
-		// Skip transformation if catalog is explicitly "ducklake" - those are queries from
-		// within the compat views that need to access the actual DuckLake information_schema
-		if n.RangeVar != nil && strings.EqualFold(n.RangeVar.Schemaname, "information_schema") &&
-			!strings.EqualFold(n.RangeVar.Catalogname, "ducklake") {
+		// Views are created in the memory.main schema so they're always accessible regardless of default catalog.
+		// Redirect all information_schema references, including catalog-qualified ones like
+		// ducklake.information_schema.columns. The compat views themselves use unqualified
+		// information_schema which resolves at query time to the default catalog, so no
+		// recursion occurs.
+		if n.RangeVar != nil && strings.EqualFold(n.RangeVar.Schemaname, "information_schema") {
 			relname := strings.ToLower(n.RangeVar.Relname)
 			if newName, ok := t.ViewMappings[relname]; ok {
 				n.RangeVar.Relname = newName