fix(opcuaclient): HistoryRead honours the per-node StatusCode (BadAggregateNotSupported + other Bad) instead of returning empty data (#649)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

docs/drivers/OpcUaClient.md

@@ -123,6 +123,13 @@ DurationGood/Bad, PercentGood/Bad, WorstQuality, NumberOfTransitions, Annotation
 population StandardDeviation/Variance — each mapped to its OPC UA Part 13 standard aggregate NodeId; #285),
 and at-time reads are supported; each
 returned `DataValue` keeps its upstream `StatusCode` and timestamps verbatim.
+**The per-node `HistoryReadResult.StatusCode` is honoured (#649).** A Bad node status is never read as
+empty data: `BadAggregateNotSupported` on a Processed read throws `HistoryAggregateNotSupportedException`, and any
+other Bad status (`BadUserAccessDenied`, `BadNodeIdUnknown`, `BadHistoryOperationUnsupported`, ...) throws
+`HistoryReadStatusException` carrying the code. The server's HistoryRead path relays both verbatim as that node's
+result status (and only that node's). `Good`, `GoodNoData`, `GoodMoreData` (continuation point) and `Uncertain`
+are unchanged, and a node-level `BadNoData` is still an empty result. Callers that previously saw an empty list for
+a refused read now see the Bad status, so an unhistorized upstream node reads `BadHistoryOperationUnsupported`.
 Event-history (`ReadEventsAsync`) is left at the interface default — the
 interface doesn't yet carry the EventFilter surface needed to forward it.