fix(mtconnect): options carry the authored tag definitions (Task 2 follow-up)

src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.MTConnect.Contracts/MTConnectDriverOptions.cs

@@ -54,6 +54,21 @@ public sealed class MTConnectDriverOptions
     /// </summary>
     public int HeartbeatMs { get; init; } = 10000;
 
+    /// <summary>
+    ///     The authored tags this driver instance serves — one <see cref="MTConnectTagDefinition"/>
+    ///     per tag, keyed by the DataItem <c>id</c> it binds
+    ///     (<see cref="MTConnectTagDefinition.FullName"/>). The factory config DTO carries these and
+    ///     builds them into the options; the driver indexes them to know each tag's target
+    ///     <see cref="MTConnectTagDefinition.DriverDataType"/> when coercing an Agent observation
+    ///     (whose wire form is always text) into a published value.
+    ///     <para>
+    ///         Defaults to <b>empty, never <c>null</c></b>: a driver instance may legitimately be
+    ///         authored with no tags yet, and a null collection here would surface as a
+    ///         NullReferenceException at deploy time from operator-authored config.
+    ///     </para>
+    /// </summary>
+    public IReadOnlyList<MTConnectTagDefinition> Tags { get; init; } = [];
+
     /// <summary>
     ///     Background connectivity-probe settings. When <see cref="MTConnectProbeOptions.Enabled"/>
     ///     is true the driver periodically issues a cheap <c>/probe</c> request and raises