SIENTIAPDE-1974

SIENTIAPDE-1974-connectors-pi-web-api: Consolidate OPC server and tag data sourcing to the tag database. This change removes the legacy opc-servers collection and enforces tag_id as the sole reference for all read and write tags via connectors and connector_tags. The Orchestrator workflow now exclusively loads OPC server and tag information from the tag database, simplifying data flow and removing conditional logic for legacy data sources. Improved error reporting for pipeline timestamp updates and updated documentation, examples, and tests are also included.

e2e/scenarios.md

@@ -70,15 +70,15 @@ Two `drift` pipelines on `frequency='1m'`: one without `interval_minutes` and wi
 
 Scenario input: `orchestrator_tag_database.json` (one `opc_ua` connector, its `connector_tags` of
 every category, one inactive, an OPC scouter reading by `tag_id` and a `predictions_batch` writing by
-`tag_id`, with a Read tag, an inactive tag, an unknown `tag_id` and a legacy entry among its write
-tags).
+`tag_id`, with a Read tag, an inactive tag, an unknown `tag_id` and an entry without `tag_id` among its
+write tags).
 
 #### 1.9.1 Write tags through the tag database
 
 `write_tags: [{tag_id}]` → `opc_output_config` keyed by `connector_id`, address and `data_type`
 from `connector_tags` (`float` when absent), `Write` → `prediction_tags`, `Prediction Confidence` →
 `confidence_tags`. The Read, inactive and unknown tags are left out and notified once
-(`ORCHESTRATOR_WRITE_TAG_NOT_FOUND_DURING_SCHEDULE_CONFIGURATION`); the legacy entry is notified
+(`ORCHESTRATOR_WRITE_TAG_NOT_FOUND_DURING_SCHEDULE_CONFIGURATION`); the entry without `tag_id` is notified
 (`ORCHESTRATOR_INVALID_WRITE_TAG_DURING_SCHEDULE_CONFIGURATION`).
 
 #### 1.9.2 A tag change redeploys its pipelines