SIENTIAPDE-1478

Enhance README and Codebase with PI Web API Integration

- Updated README.md to include details about PI Web API integration, including configuration and export capabilities.
- Modified Activities class to incorporate PI Web API export operations and error handling.
- Added new API class for handling PI Web API interactions, including writing prediction and confidence data.
- Updated prediction workflows to support PI Web API output configuration.
- Enhanced worker and sub-workflows to include PI Web API in task queues and export processes.
- Improved documentation and error handling for PI Web API connections and configurations.

laborious/activities/activities.py

@@ -24,15 +24,18 @@ class Activities(Storage, MLFlow, Gates, OPC, ModelMetrics, API):
     MLFlow model interactions, data quality validation, and OPC server communications.
 
     The class implements multiple inheritance to combine specialized functionality:
-    - Postgres: Database operations and data persistence
+    - Storage: Database operations and data persistence
     - MLFlow: Model inference and transformation operations
     - Gates: Data quality validation and filtering mechanisms
     - OPC: Real-time data export to OPC servers
+    - ModelMetrics: Model performance metrics and drift detection
+    - API: PI Web API export operations for industrial systems
 
     Attributes:
         postgres_config (dict): PostgreSQL connection configuration
         mlflow_config (dict): MLFlow server configuration
         opc_config (dict): OPC server configuration
+        pi_web_api_config (dict): PI Web API server configuration
         logger (Logger): Logging and observability instance
         notification_handler (NotificationHandler): Notification management instance
     """
@@ -137,6 +140,8 @@ class Activities(Storage, MLFlow, Gates, OPC, ModelMetrics, API):
         This method ensures proper cleanup of all resources including:
         - PostgreSQL connection pools
         - OPC server connections
+        - PI Web API client connections
+        - MLFlow model repositories
         - Any other resources that need explicit cleanup
 
         The method should be called before the application terminates to ensure