fix(drivers): flip runtime tag parsers to strict enum parsing (#457)

R2-11 Phase C. All six equipment-tag parsers (Modbus/S7/AbCip/AbLegacy/
TwinCAT/Focas) now read enum fields via the new TagConfigJson.TryReadEnumStrict:
absent -> fallback, valid -> parsed, present-but-invalid (typo) -> TryParse
returns false -> EquipmentTagRefResolver.TryResolve false -> driver surfaces
BadNodeIdUnknown, instead of the old lenient path that silently defaulted a
typo to a wrong-width Good.

Modbus flips all three enum fields (region/dataType/byteOrder); the other five
flip dataType. The deploy-time Deployment:TagConfigValidationMode=Error gate is
unchanged and remains the operator pre-flight.

Coverage:
- Six *EquipmentTagParserStrictnessTests inverted from Freeze_typo_* (lenient)
  to Typo_*_rejects_the_tag + Valid_*_still_parses.
- TagConfigJsonTests.TryReadEnumStrict_rejects_only_invalid matrix.
- Driver-level end-to-end proof:
  AbCipEquipmentTagTests.Driver_read_of_a_typod_dataType_ref_surfaces_BadNodeIdUnknown
  drives the real AbCipDriver.ReadAsync through resolve->status.

Golden parity corpus has no typo'd enums, so the flip is a no-op there.
Full solution builds clean; all six driver suites + core + parity + gate green.

tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Modbus.Tests/ModbusEquipmentTagParserStrictnessTests.cs

@@ -5,19 +5,45 @@ using ZB.MOM.WW.OtOpcUa.Driver.Modbus;
 namespace ZB.MOM.WW.OtOpcUa.Driver.Modbus.Tests;
 
 /// <summary>
-///     R2-11 (05/CONV-2) strictness surface for the Modbus equipment-tag parser: the runtime stays lenient
-///     (freeze), the new <c>Inspect</c> reports the silently-defaulted typo, and the <c>writable</c> key is
-///     now honoured (default true).
+///     R2-11 Phase C strictness surface for the Modbus equipment-tag parser: the runtime is now STRICT — a
+///     present-but-invalid (typo'd) enum on any of the three enum fields (<c>region</c> / <c>dataType</c> /
+///     <c>byteOrder</c>) rejects the whole tag (<c>TryParse</c> ⇒ <see langword="false"/> ⇒
+///     <c>BadNodeIdUnknown</c>) instead of silently defaulting to a wrong-width <c>Good</c>. <c>Inspect</c>
+///     still reports the same typo at deploy time, and the <c>writable</c> key is honoured (default true).
 /// </summary>
 public sealed class ModbusEquipmentTagParserStrictnessTests
 {
-    // ---- Phase-A behaviour freeze: a typo'd enum still silently defaults ----
+    // ---- Phase C: a typo'd enum now rejects the tag (BadNodeIdUnknown), not a silent default ----
 
     [Fact]
-    public void Freeze_typo_dataType_still_defaults_to_Int16()
+    public void Typo_dataType_rejects_the_tag()
     {
         ModbusEquipmentTagParser.TryParse(
-            "{\"region\":\"HoldingRegisters\",\"address\":1,\"dataType\":\"Intt16\"}", out var def)
+            "{\"region\":\"HoldingRegisters\",\"address\":1,\"dataType\":\"Intt16\"}", out _)
+            .ShouldBeFalse();
+    }
+
+    [Fact]
+    public void Typo_region_rejects_the_tag()
+    {
+        ModbusEquipmentTagParser.TryParse(
+            "{\"region\":\"HoldingRegisterz\",\"address\":1,\"dataType\":\"Int16\"}", out _)
+            .ShouldBeFalse();
+    }
+
+    [Fact]
+    public void Typo_byteOrder_rejects_the_tag()
+    {
+        ModbusEquipmentTagParser.TryParse(
+            "{\"region\":\"HoldingRegisters\",\"address\":1,\"dataType\":\"Int16\",\"byteOrder\":\"BigEndan\"}", out _)
+            .ShouldBeFalse();
+    }
+
+    [Fact]
+    public void Valid_enums_still_parse()
+    {
+        ModbusEquipmentTagParser.TryParse(
+            "{\"region\":\"HoldingRegisters\",\"address\":1,\"dataType\":\"Int16\",\"byteOrder\":\"BigEndian\"}", out var def)
             .ShouldBeTrue();
         def.DataType.ShouldBe(ModbusDataType.Int16);
     }