Add client-side failover to CLI tool for redundancy testing

All commands gain --failover-urls (-F) to specify alternate endpoints.
Short-lived commands try each URL in order on initial connect. The
subscribe command monitors KeepAlive and automatically reconnects to
the next available server, re-creating the subscription on failover.
Verified with live service start/stop: primary down triggers failover
to secondary, primary restart allows failback.

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

tools/opcuacli-dotnet/Commands/AlarmsCommand.cs

@@ -24,6 +24,9 @@ public class AlarmsCommand : ICommand
     [CommandOption("security", 'S', Description = "Transport security: none, sign, encrypt (default: none)")]
     public string Security { get; init; } = "none";
 
+    [CommandOption("failover-urls", 'F', Description = "Comma-separated failover endpoint URLs for redundancy")]
+    public string? FailoverUrls { get; init; }
+
     /// <summary>
     /// Gets the node to subscribe to for event notifications, typically a source object or the server node.
     /// </summary>
@@ -48,7 +51,9 @@ public class AlarmsCommand : ICommand
     /// <param name="console">The CLI console used for cancellation and alarm-event output.</param>
     public async ValueTask ExecuteAsync(IConsole console)
     {
-        using var session = await OpcUaHelper.ConnectAsync(Url, Username, Password, Security);
+        var urls = FailoverUrlParser.Parse(Url, FailoverUrls);
+        using var failover = new OpcUaFailoverHelper(urls, Username, Password, Security);
+        using var session = await failover.ConnectAsync();
 
         var nodeId = string.IsNullOrEmpty(NodeId)
             ? ObjectIds.Server