fix(sql): bind string keys untyped on Postgres so integer key columns compare (#602 STAB-24)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

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

@@ -64,6 +64,21 @@ public sealed class PostgresDialect : ISqlDialect
         // Intentionally empty: see the summary.
     }
 
+    /// <summary>
+    ///     STAB-24: a string-valued bind is sent with <see cref="NpgsqlTypes.NpgsqlDbType.Unknown"/> so the
+    ///     server infers its type from the compared column. Bound as the default <c>text</c>, a tag whose
+    ///     <c>keyValue</c> is <c>"3"</c> against an <c>integer</c> key column fails with
+    ///     <c>operator does not exist: integer = text</c>. Unknown still carries the value as data — it is
+    ///     never interpolated — so the injection boundary is unchanged.
+    /// </summary>
+    /// <param name="parameter">The parameter to adjust.</param>
+    /// <param name="value">The authored value.</param>
+    public void ConfigureParameter(DbParameter parameter, object? value)
+    {
+        if (parameter is NpgsqlParameter npgsql && value is string)
+            npgsql.NpgsqlDbType = NpgsqlTypes.NpgsqlDbType.Unknown;
+    }
+
     /// <summary>
     ///     65535 — the extended-query protocol carries the parameter count as a signed/unsigned 16-bit field
     ///     in <c>Bind</c>, so that is a protocol ceiling rather than a server setting, and Npgsql raises it