Add iceberg v2 consumer for flattened data consuming, schema will be inferred by arrow

Author: ismailsimsek

README.md

@@ -30,7 +30,8 @@ The Iceberg handlers are designed to stream CDC events directly into Apache Iceb
 *   `IcebergChangeHandler`: A straightforward handler that appends change data to a source-equivalent Iceberg table using a predefined schema.
     *   **Use Case**: Best for creating a "bronze" layer where you want to capture the raw Debezium event. The `before` and `after` payloads are stored as complete JSON strings.
     *   **Schema**: Uses a fixed schema where complex nested fields (`source`, `before`, `after`) are stored as `StringType`. It also includes helpful metadata columns (`_consumed_at`, `_dbz_event_key`, `_dbz_event_key_hash`) for traceability.
-      * With consuming data as json, all source syste schema changes will be absorbed automatically. 
+        *   With consuming data as json, all source syste schema changes will be absorbed automatically.
+        *   **Automatic Table Creation & Partitioning**: **It automatically creates a new Iceberg table for each source table** and partitions it by day on the `_consumed_at` timestamp for efficient time-series queries.
 
 *   `IcebergChangeHandlerV2`: A more advanced handler that automatically infers the schema from the Debezium events and creates a well-structured Iceberg table accordingly.
     *   **Use Case**: Ideal for scenarios where you want the pipeline to automatically create tables with native data types that mirror the source. This allows for direct querying of the data without needing to parse JSON.