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/OracleDialect.cs

@@ -103,6 +103,16 @@ public sealed class OracleDialect : ISqlDialect
         if (command is OracleCommand oracle) oracle.BindByName = true;
     }
 
+    /// <summary>
+    ///     1000 — <b>the tightest of the three ceilings, and the one that actually binds.</b> Oracle allows
+    ///     64k bind variables per statement, but an <c>IN</c> <em>expression list</em> is limited to 1000
+    ///     entries (<c>ORA-01795</c>), and the key-value model's <c>IN (:p_k0, …)</c> list is the only
+    ///     variable-length parameter list this driver emits. The seam therefore reports the limit the caller
+    ///     will hit rather than the larger one it never reaches — a dialect that reported 64000 here would be
+    ///     technically accurate and would still produce a statement the server refuses.
+    /// </summary>
+    public int MaxBindParameters => 1000;
+
     /// <summary>Oracle has no bare <c>SELECT</c>; every projection needs a table, and <c>DUAL</c> is the one-row one.</summary>
     public string LivenessSql => "SELECT 1 FROM DUAL";