Complete dbt-fusion Redshift temp table workaround

The previous fix (62b1122) only covered create_intermediate_relation(),
but test materializations and other paths still created temp tables,
causing the same ADBC 0.22 panic.

This adds redshift__edr_get_create_table_as_sql() to intercept ALL
temporary table creation in Redshift+fusion, creating regular tables
instead. These are cleaned up by Elementary's normal cleanup logic.

Fixes all remaining instances of:
  panic: "Either resolved_catalog or resolved_schema must be present"
  at fs/sa/crates/dbt-adapter/src/metadata/mod.rs:91:9

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

Author: haritamar

macros/utils/table_operations/create_table_as.sql

@@ -46,6 +46,23 @@
   as {{ sql_query }}
 {% endmacro %}
 
+{% macro redshift__edr_get_create_table_as_sql(temporary, relation, sql_query) %}
+  {% if temporary and elementary.is_dbt_fusion() %}
+    {# Workaround for dbt-fusion 2.0.0-preview.104 ADBC 0.22 bug
+       where metadata queries on temp tables return empty catalog/schema
+       causing panic: "Either resolved_catalog or resolved_schema must be present"
+       at fs/sa/crates/dbt-adapter/src/metadata/mod.rs:91:9
+
+       Create regular tables instead of temporary when using dbt-fusion.
+       These will be cleaned up normally by Elementary's cleanup logic. #}
+    create or replace table {{ relation }}
+    as {{ sql_query }}
+  {% else %}
+    create {% if temporary %} temporary {% endif %} table {{ relation.include(database=(not temporary), schema=(not temporary)) }}
+    as {{ sql_query }}
+  {% endif %}
+{% endmacro %}
+
 {% macro databricks__edr_get_create_table_as_sql(temporary, relation, sql_query) %}
   {% if temporary %}
     {% if elementary.is_dbt_fusion() %}

macros/utils/table_operations/has_temp_table_support.sql

@@ -28,13 +28,13 @@
 
 {% macro redshift__has_temp_table_support() %}
     {# Workaround for dbt-fusion 2.0.0-preview.104 ADBC 0.22 bug
-       where get_columns_in_relation returns empty catalog/schema for temp tables
+       where metadata queries on temp tables return empty catalog/schema
        causing panic: "Either resolved_catalog or resolved_schema must be present"
        at fs/sa/crates/dbt-adapter/src/metadata/mod.rs:91:9
 
-       This occurs intermittently during INSERT operations on temporary tables.
-       Disabling temp tables for Redshift+fusion uses regular tables instead,
-       which is slightly less efficient but avoids the panic.
+       This disables temp tables for create_intermediate_relation(),
+       and redshift__edr_get_create_table_as_sql() handles other paths
+       that create temp tables (like test materializations).
 
        Bug introduced in preview.104, not present in preview.102.
        TODO: Re-enable once dbt-fusion fixes this in a future release. #}