SIENTIAPDE-1478

Refactor PIWebAPIClient and Update Configuration Imports

- Removed outdated PostgreSQL, Redis, MongoDB, and API configuration functions from connectors_config.py.
- Deleted the pi_web_api_client.py file as part of the refactor.
- Updated imports in worker.py and api.py to use the new repository structure.
- Cleaned up scenarios.md by removing obsolete scenarios related to unique constraint violations.
- Commented out the specific version of the sientia-dataops-library in requirements.txt for flexibility.

e2e/scenarios.md

@@ -338,25 +338,6 @@ The `pi_web_api_scouter` workflow:
 
 ---
 
-#### Scenario 2.3.2: PostgreSQL Unique Constraint Violation
-**Description**: Duplicate data violates unique constraint
-
-**Input**:
-- Data with duplicate `model_id`, `timestamp`, `variable` combination
-- `on_conflict: 'ignore'` configured
-
-**Expected Behavior**:
-- PostgreSQL handles conflict with `ON CONFLICT DO NOTHING`
-- `affected_rows` may be 0 for duplicates
-- Workflow continues normally
-
-**Assertions**:
-- No exception raised
-- Duplicates ignored
-- Workflow continues
-
----
-
 ## 3. Activity-Specific Scenarios
 
 > **Note**: Activity-specific scenarios are better suited for unit tests rather than e2e tests.
@@ -457,7 +438,6 @@ For each scenario, verify:
 2. Scenario 2.1.2: Quality Filters
 3. Scenario 2.1.3: Different Aggregations
 4. Scenario 3.3.5: Invalid Aggregation
-5. Scenario 3.5.2: Conflict Ignore
 
 ### Low Priority (Nice to Have)
 1. Scenario 4.1.2: Retry Success