fix(drivers): ResolveHost resolves equipment-tag refs via EquipmentTagRefResolver — per-host breaker isolation (CONV-4)

src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.TwinCAT/TwinCATDriver.cs

@@ -706,10 +706,20 @@ public sealed class TwinCATDriver : IDriver, IReadable, IWritable, ITagDiscovery
     /// </summary>
     public const string UnresolvedHostSentinel = "";
 
-    /// <inheritdoc />
+    /// <summary>
+    ///     Resolve a reference to the device host that keys its per-host resilience
+    ///     (bulkhead / circuit breaker). CONV-4: routes through
+    ///     <see cref="EquipmentTagRefResolver{TDef}"/> so an equipment-tag reference (raw TagConfig
+    ///     JSON) resolves to its OWN authored device rather than the first-device fallback. The
+    ///     empty-host guard keeps an address-less equipment tag on the fallback rather than keying
+    ///     the <see cref="UnresolvedHostSentinel"/>. The resolver caches parses, so this adds no
+    ///     per-call cost after first use.
+    /// </summary>
+    /// <param name="fullReference">The tag reference (authored name or equipment-tag JSON).</param>
+    /// <returns>The device host key.</returns>
     public string ResolveHost(string fullReference)
     {
-        if (_tagsByName.TryGetValue(fullReference, out var def))
+        if (_resolver.TryResolve(fullReference, out var def) && !string.IsNullOrEmpty(def.DeviceHostAddress))
             return def.DeviceHostAddress;
         // First device's HostAddress when one exists; otherwise the unresolved sentinel —
         // intentionally NOT DriverInstanceId, which is a config-DB key, not a host address.