test(scripting): pin the Scripting section bind behind one helper

Review m-1. The bind moves from Program.cs into
Host.Configuration.ScriptingOptionsBinding.Bind, which binds the
section and clamps it. Program.cs calls it, and
ScriptingOptionsBindingTests drives it with in-memory configuration.
Every documented key takes a non-default value, so a misspelled
property or key goes red instead of silently falling back to the
defaults. The tests also cover a clamped bind (1e300 / 1024 / 0, three
adjustments), an absent section, and the sibling LogFilePath /
LogTopicMinLevel keys leaving the bind untouched.

Refs #731 #734
Claude-Session: https://claude.ai/code/session_01Ub9hGmYLQvn9XETzw7CMsT

src/Server/ZB.MOM.WW.OtOpcUa.Host/Program.cs

@@ -370,8 +370,8 @@ if (hasDriver)
     // Warning rather than an OverflowException inside a script run. The one instance is shared by every script
     // seam on the node: the virtual-tag evaluator below, the scripted-alarm engine (DriverHostActor, via
     // WithOtOpcUaRuntimeActors) and every Calculation driver (DriverFactoryBootstrap).
-    var scriptingOptions = (builder.Configuration.GetSection(ScriptingOptions.SectionName).Get<ScriptingOptions>()
-        ?? new ScriptingOptions()).Sanitized(out var scriptingAdjustments);
+    var scriptingOptions = ZB.MOM.WW.OtOpcUa.Host.Configuration.ScriptingOptionsBinding.Bind(
+        builder.Configuration, out var scriptingAdjustments);
     foreach (var adjustment in scriptingAdjustments)
         Log.Warning("Scripting misconfiguration detected at startup: {Adjustment}", adjustment);
     builder.Services.AddSingleton(scriptingOptions);