fix(driver-twincat): resolve Low code-review findings (Driver.TwinCAT-004,006,014,015,016)

- Driver.TwinCAT-004: corrected the IEC time-type inline comments;
  documented that the driver currently surfaces them as raw UInt32
  counters.
- Driver.TwinCAT-006: ResolveHost returns a documented UnresolvedHost
  sentinel when no devices are configured instead of returning the
  logical DriverInstanceId (which never matches GetHostStatuses).
- Driver.TwinCAT-014: wired Probe.Timeout into the probe-loop call and
  added a NotificationMaxDelayMs config knob threaded through
  AddNotificationAsync.
- Driver.TwinCAT-015: Dispose() runs a genuinely synchronous teardown
  with bounded waits (no sync-over-async deadlock pattern).
- Driver.TwinCAT-016: pinned the Structure-tag rejection and the
  probe-loop vs read disposal race with regression tests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.TwinCAT/TwinCATDriverOptions.cs

@@ -32,6 +32,16 @@ public sealed class TwinCATDriverOptions
     ///     the strict-config path for deployments where only declared tags should appear.
     /// </summary>
     public bool EnableControllerBrowse { get; init; }
+
+    /// <summary>
+    ///     Maximum batching delay in milliseconds for ADS device notifications. Passed to
+    ///     <c>NotificationSettings</c> as the max-delay value: TwinCAT may coalesce notifications
+    ///     up to this delay before pushing them. <c>0</c> (default) = no batching, push
+    ///     immediately. Useful for high-churn signals where the OPC UA subscriber tolerates a
+    ///     small delay in exchange for fewer wire round-trips. Listed in <c>docs/v2/driver-specs.md</c>
+    ///     section 6 — was previously hard-coded to 0 (Driver.TwinCAT-014).
+    /// </summary>
+    public int NotificationMaxDelayMs { get; init; }
 }
 
 /// <summary>