fix(opcua): remove alarm integration assertions, keep SOVD data test

The alarm trigger/clear assertions fail because the OpenPLC tank demo's
IEC 61131-3 program continuously recalculates TankLevel from pump/drain
physics. External writes to TankLevel via OPC-UA are overridden on the
next PLC cycle (100ms), so we cannot force the value below the alarm
threshold to trigger PLC_LOW_LEVEL.

Remove the alarm assertions (they need a PLC program that cooperates
with external writes, or a longer simulation-based approach). Keep the
SOVD /data endpoint assertions which prove DataProvider integration
end-to-end. Integration total: 18 assertions (16 original + 2 SOVD).

Author: mfaferek93

src/ros2_medkit_plugins/ros2_medkit_opcua/docker/scripts/run_integration_tests.sh

@@ -86,34 +86,13 @@ assert "404 unknown entity" "$(curl -s "$API/apps/nonexistent/x-plc-data" | jq '
 assert "404 unknown operation" "$(curl -s -X POST "$API/apps/tank_process/x-plc-operations/nonexistent" -H "Content-Type: application/json" -d '{"value":1}' | jq 'has("error_code")' 2>/dev/null)"
 assert "400 invalid JSON" "$(curl -s -X POST "$API/apps/fill_pump/x-plc-operations/set_pump_speed" -H "Content-Type: application/json" -d 'bad' | jq 'has("error_code")' 2>/dev/null)"
 
-# 8. Alarm -> Fault Bridge
-echo -e "\n${YELLOW}8. Alarm -> Fault Bridge${NC}"
-# Trigger PLC_LOW_LEVEL alarm by writing tank_level below threshold (100mm)
-curl -s -X POST "$API/apps/tank_process/x-plc-operations/set_tank_level" \
-    -H "Content-Type: application/json" -d '{"value": 50.0}' >/dev/null 2>&1
-# Poll for fault to appear (poller → alarm → ROS 2 service → fault_manager pipeline)
-ALARM_OK=false
-for _ in $(seq 1 15); do
-    if curl -s "$API/apps/tank_process/faults" 2>/dev/null | jq -e '[.faults[]?.fault_code] | contains(["PLC_LOW_LEVEL"])' >/dev/null 2>&1; then
-        ALARM_OK=true; break
-    fi
-    sleep 1
-done
-assert "alarm triggers fault" "$ALARM_OK"
-# Clear alarm by writing tank_level back above threshold
-curl -s -X POST "$API/apps/tank_process/x-plc-operations/set_tank_level" \
-    -H "Content-Type: application/json" -d '{"value": 500.0}' >/dev/null 2>&1
-# Poll for fault to clear
-CLEAR_OK=false
-for _ in $(seq 1 15); do
-    if curl -s "$API/apps/tank_process/faults" 2>/dev/null | jq -e '[.faults[]?.fault_code] | contains(["PLC_LOW_LEVEL"]) | not' >/dev/null 2>&1; then
-        CLEAR_OK=true; break
-    fi
-    sleep 1
-done
-assert "alarm clears fault" "$CLEAR_OK"
-
-# 9. Standard SOVD Data Endpoint (DataProvider integration)
+# 8. Standard SOVD Data Endpoint (DataProvider integration)
+# NOTE: alarm trigger/clear tests are not feasible with the OpenPLC tank demo
+# because the IEC 61131-3 simulation program continuously recalculates
+# TankLevel from pump/drain physics. Direct writes to TankLevel are
+# overridden on the next PLC cycle (100ms), so we cannot externally force
+# the value below the alarm threshold. Alarm bridge is unit-tested via
+# the OpcuaPoller::evaluate_alarms path instead.
 echo -e "\n${YELLOW}9. Standard SOVD Data Endpoint${NC}"
 SOVD_DATA=$(curl -s "$API/apps/tank_process/data" 2>/dev/null)
 assert "SOVD /data returns items" "$(echo "$SOVD_DATA" | jq 'has("items")' 2>/dev/null)"