refactor(dbt): Align csv_to_postgres scenario with community conventions

Follow-up to PR OpenLineage#186 feedback addressing final alignment issues:
- Rename csv_to_postgres_local to csv_to_postgres (removes 'local' qualifier)
- Remove README.md from scenario (community pattern uses scenario.md only)
- Update documentation to reflect CI/CD service container deployment model
- Correct residual DuckDB references to PostgreSQL

Refs: OpenLineage#186
Signed-off-by: roller100 (BearingNode) <[email protected]>

Author: roller100 (BearingNode)

producer/dbt/README.md

@@ -154,7 +154,7 @@ If you need to debug event generation locally:
     ```bash
     # Using the test runner CLI (same as GitHub Actions uses)
     python test_runner/cli.py run-scenario \
-      --scenario csv_to_postgres_local \
+      --scenario csv_to_postgres \
       --output-dir ./test_output/$(date +%s)
 
     # List available scenarios

…narios/csv_to_postgres_local/config.json …bt/scenarios/csv_to_postgres/config.jsonproducer/dbt/scenarios/csv_to_postgres_local/config.json renamed to producer/dbt/scenarios/csv_to_postgres/config.json producer/dbt/scenarios/csv_to_postgres_local/config.json renamed to producer/dbt/scenarios/csv_to_postgres/config.json

@@ -1,8 +1,8 @@
-# CSV to PostgreSQL Local Scenario
+# CSV to PostgreSQL Scenario
 
 ## Overview
 
-This scenario validates dbt's OpenLineage integration compliance using synthetic test data in a controlled CSV → dbt → PostgreSQL pipeline with local file transport.
+This scenario validates dbt's OpenLineage integration compliance using synthetic test data in a controlled CSV → dbt → PostgreSQL pipeline with file transport.
 
 **Purpose**: Compatibility testing and validation, not production use case demonstration.
 
@@ -40,8 +40,8 @@ Synthetic customer analytics scenario designed for validation testing:
 
 - **Source**: Synthetic CSV files with test customer and order data
 - **Transform**: dbt models with staging and analytics layers
-- **Target**: DuckDB database (local file)
-- **Transport**: OpenLineage file transport (JSONL events)
+- **Target**: PostgreSQL database (CI/CD service container)
+- **Transport**: OpenLineage file transport (JSON Lines format)
 - **Validation**: Comprehensive facet compliance testing
 
 ## Expected Outputs

…s_local/events/column_lineage_event.json …ostgres/events/column_lineage_event.jsonproducer/dbt/scenarios/csv_to_postgres_local/events/column_lineage_event.json renamed to producer/dbt/scenarios/csv_to_postgres/events/column_lineage_event.json producer/dbt/scenarios/csv_to_postgres_local/events/column_lineage_event.json renamed to producer/dbt/scenarios/csv_to_postgres/events/column_lineage_event.json

@@ -46,11 +46,11 @@ The atomic test runner validates:
 
 1. **Environment Availability**
    - dbt command availability
-   - DuckDB Python package installation
+   - PostgreSQL adapter package installation
 
 2. **dbt Project Creation**
    - Minimal dbt project structure
-   - Profile configuration for DuckDB
+   - Profile configuration for PostgreSQL
 
 3. **dbt Execution**
    - Model compilation and execution
@@ -62,7 +62,7 @@ The atomic test runner validates:
 
 ## CLI Commands
 
-- `check-environment`: Verify dbt and DuckDB availability
+- `check-environment`: Verify dbt and PostgreSQL adapter availability
 - `run-atomic`: Run all atomic validation tests
 - `setup`: Install dependencies (requires virtual environment)
 
@@ -73,6 +73,6 @@ This test runner provides the foundation for OpenLineage event validation. When
 ## Troubleshooting
 
 1. **Python Environment Issues**: Use virtual environment as shown above
-2. **dbt Not Found**: Install dbt-core and dbt-duckdb in your environment
-3. **DuckDB Issues**: Ensure duckdb Python package is installed
+2. **dbt Not Found**: Install dbt-core and dbt-postgres in your environment
+3. **PostgreSQL Issues**: Ensure psycopg2-binary Python package is installed
 4. **Permission Errors**: Make sure scripts are executable (`chmod +x`)