Tentatively disallowed normalization for DuckDB (#22528)

Author: ryankfu

airbyte-config/init/src/main/resources/seed/destination_definitions.yaml

@@ -449,9 +449,4 @@
   dockerImageTag: 0.1.0
   documentationUrl: https://docs.airbyte.io/integrations/destinations/duckdb
   icon: duckdb.svg
-  normalizationConfig:
-    normalizationRepository: airbyte/normalization-duckdb
-    normalizationTag: 0.2.25
-    normalizationIntegrationType: duckdb
-  supportsDbt: true
   releaseStage: alpha

airbyte-integrations/bases/base-normalization/integration_tests/dbt_integration_test.py

@@ -59,8 +59,6 @@ def setup_db(self, destinations_to_test: List[str]):
             self.setup_clickhouse_db()
         if DestinationType.TIDB.value in destinations_to_test:
             self.setup_tidb_db()
-        if DestinationType.DUCKDB.value in destinations_to_test:
-            self.setup_duckdb_db()
 
     def setup_postgres_db(self):
         start_db = True

docs/integrations/destinations/duckdb.md

@@ -19,7 +19,7 @@ This destination writes data to a file on the _local_ filesystem on the host run
 
 If you set [Normalization](https://docs.airbyte.com/understanding-airbyte/basic-normalization/), source data will be normalized to a tabular form. Let's say you have a source such as GitHub with nested JSONs; the Normalization ensures you end up with tables and columns. Suppose you have a many-to-many relationship between the users and commits. Normalization will create separate tables for it. The end state is the [third normal form](https://en.wikipedia.org/wiki/Third_normal_form) (3NF).
 
-If turn off the Normalization, each stream will be output into its own table `_airbyte_raw_{stream_name}`. Each table will contain 3 columns:
+Each table will contain 3 columns:
 
 * `_airbyte_ab_id`: a uuid assigned by Airbyte to each event that is processed.
 * `_airbyte_emitted_at`: a timestamp representing when the event was pulled from the data source.