[dagster-dbt] Gracefully skip insights on unsupported adapters in with_insights (#25440)

## Summary & Motivation

Matches the behavior of `.with_insights()` chained method with the older `dbt_with_snowflake_insights()` method for generating dbt snowflake insights, where calling the method on an adapter that doesn't support cost insights raises a warning instead of an error (since there are cases, like with out demo, where you want to use different database engines without changing the code).

## Test Plan

BK

## Changelog

- [dagster-dbt] using the `.with_insights()` method now sends a warning instead of an error if you are not using a supported adapter

Internal-RevId: 51a35ce08ae3101758315258f3ff1c5badc48280

Author: cnolanminich

python_modules/libraries/dagster-dbt/dagster_dbt/core/dbt_event_iterator.py

@@ -326,7 +326,9 @@ def with_insights(
         record_observation_usage: bool = True,
     ) -> "DbtEventIterator[DbtDagsterEventType]":
         """Associate each warehouse query with the produced asset materializations for use in Dagster
-        Plus Insights. Currently supports Snowflake and BigQuery.
+        Plus Insights. Currently supports Snowflake and BigQuery. For any other adapter (e.g.
+        DuckDB), this is a no-op: a warning is logged and the dbt events pass through unchanged,
+        so the same pipeline can run locally against an unsupported warehouse without failing.
 
         For more information, see the documentation for
         `dagster_cloud.dagster_insights.dbt_with_snowflake_insights` and
@@ -393,6 +395,12 @@ def jaffle_shop_dbt_assets(
                 dbt_cli_invocation=self._dbt_cli_invocation,
             )
         else:
-            check.failed(
-                f"The `with_insights` method is only supported for Snowflake and BigQuery and is not supported for adapter type `{adapter_type}`"
+            logger.warning(
+                "Dagster+ Insights is only supported for the Snowflake and BigQuery dbt"
+                f" adapters, but the dbt project uses the `{adapter_type}` adapter. Skipping"
+                " insights; dbt events will pass through unchanged."
+            )
+            return DbtEventIterator(
+                events=self,
+                dbt_cli_invocation=self._dbt_cli_invocation,
             )

python_modules/libraries/dagster-dbt/dagster_dbt_tests/core/test_postprocessing.py

@@ -10,7 +10,6 @@
     _check as check,
     materialize,
 )
-from dagster._check import CheckError
 from dagster._core.definitions.events import AssetMaterialization, Output
 from dagster._core.definitions.metadata.metadata_value import MetadataValue, TableMetadataValue
 from dagster._core.definitions.metadata.table import TableRecord
@@ -138,21 +137,27 @@ def my_dbt_assets(context: AssetExecutionContext, dbt: DbtCliResource):
     ), str(metadata_by_asset_key)
 
 
-def test_insights_err_not_snowflake_or_bq(
+def test_insights_skips_unsupported_adapter(
     test_jaffle_shop_manifest_standalone_duckdb_dbfile: dict[str, Any],
     caplog: pytest.LogCaptureFixture,
 ) -> None:
+    # On an unsupported adapter (here, DuckDB), `with_insights` is a graceful no-op: it logs a
+    # warning and passes the dbt events through unchanged rather than failing the run.
     @dbt_assets(manifest=test_jaffle_shop_manifest_standalone_duckdb_dbfile)
     def my_dbt_assets(context: AssetExecutionContext, dbt: DbtCliResource):
         yield from dbt.cli(["build"], context=context).stream().with_insights()
 
-    with pytest.raises(CheckError) as exc_info:
-        materialize(
-            [my_dbt_assets],
-            resources={"dbt": DbtCliResource(project_dir=os.fspath(test_jaffle_shop_path))},
-        )
+    result = materialize(
+        [my_dbt_assets],
+        resources={"dbt": DbtCliResource(project_dir=os.fspath(test_jaffle_shop_path))},
+    )
 
-    assert "is not supported for adapter type `duckdb`" in str(exc_info.value)
+    assert result.success
+    assert any(
+        "Insights is only supported for the Snowflake and BigQuery dbt adapters" in record.message
+        and "`duckdb`" in record.message
+        for record in caplog.records
+    ), [record.message for record in caplog.records]
 
 
 @pytest.mark.parametrize(