fix(sql): chunk the key-value IN list at the dialect's bind ceiling (Driver.Sql-002, Driver.Sql.Dialect-002)

ISqlDialect gains MaxBindParameters — the per-command ceiling the seam was
missing while modelling everything else that differs per backend: 2098 usable
of SQL Server's 2100 (sp_executesql spends two), 1000 for Oracle's IN-list
limit (ORA-01795, tighter than its 64k bind count), 65535 for the Postgres
Bind message.

SqlGroupPlanner.AddKeyValuePlans now emits several plans for one group when
its distinct keys exceed that ceiling, instead of one statement the provider
refuses after the connection opened — which left every tag in an EAV group
publishing BadCommunicationError on every poll, permanently, and reported the
database endpoint as down. Chunks share the group key; members follow their
own key so a shared keyValue never splits. SqlPollReader is unchanged: it runs
one command per plan and slices each plan's own Members back, proven by a
fixture read at a ceiling of 1.

src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Sql.Dialect/SqlServerDialect.cs

@@ -59,6 +59,15 @@ public sealed class SqlServerDialect : ISqlDialect
         // Intentionally empty: see the summary.
     }
 
+    /// <summary>
+    ///     2098 — SQL Server's hard cap is <b>2100 parameters per statement</b>, and
+    ///     <c>Microsoft.Data.SqlClient</c> spends two of them itself: a parameterized command is executed
+    ///     through <c>sp_executesql</c>, whose first two arguments are the statement text and the parameter
+    ///     declaration list. A caller filling 2100 would therefore be rejected with
+    ///     <c>"The incoming request has too many parameters"</c> for a limit it appeared to respect.
+    /// </summary>
+    public int MaxBindParameters => 2098;
+
     /// <inheritdoc/>
     public string LivenessSql => "SELECT 1";