fix(dcl): apply native-alarm conditionFilter (client-side gate + OPC UA WhereClause) (#8)

conditionFilter was plumbed end-to-end but applied nowhere — a filtered source
silently mirrored all conditions. Define the filter as a comma-separated,
case-insensitive list of condition type names (blank = all); enforce it
authoritatively client-side in DataConnectionActor routing (uniform across OPC UA
+ MxGateway) and, for OPC UA, additionally build a server-side EventFilter
WhereClause as a bandwidth optimization.

src/ZB.MOM.WW.ScadaBridge.DataConnectionLayer/Adapters/MxGatewayDataConnection.cs

@@ -163,7 +163,11 @@ public class MxGatewayDataConnection : IDataConnection, IBrowsableDataConnection
                 _alarmCts = new CancellationTokenSource();
                 var token = _alarmCts.Token;
                 var client = _client!;
-                // Gateway-wide feed (null prefix); the actor filters per source reference.
+                // Gateway-wide feed (null prefix). The MxGateway has no server-side
+                // condition filter, so conditionFilter is intentionally NOT forwarded
+                // here: the DataConnectionActor applies it as the authoritative
+                // client-side gate per source reference AND per condition type
+                // (M2.4 / #8 — AlarmConditionFilter), uniform with the OPC UA path.
                 _ = Task.Run(() => client.RunAlarmStreamAsync(null, t => callback(t), token), token);
             }
         }