refactor(opcuaserver): rename Phase7* address-space pipeline to AddressSpace*

The OPC UA address-space build pipeline was named after a v2-roadmap
milestone number rather than its domain. Rename the family to describe
what it does (build/diff/apply the OPC UA address space):

  Phase7Composer          -> AddressSpaceComposer
  Phase7CompositionResult -> AddressSpaceComposition
  Phase7Planner           -> AddressSpacePlanner
  Phase7Plan              -> AddressSpacePlan
  Phase7Applier           -> AddressSpaceApplier
  Phase7ApplyOutcome      -> AddressSpaceApplyOutcome

The 9 Phase7*Tests suites follow suit; Phase7ScriptingEntitiesTests ->
ScriptingEntitiesTests (it tests the scripting migration, not the
pipeline). Log-message prefixes move to the new class names.

Pure mechanical rename, no behavioral change. EF migration classes/IDs
(AddPhase7ScriptingTables, ExtendComputeGenerationDiffWithPhase7) are
immutable and left untouched, as are historical design docs.

Build clean; OpcUaServer 261/261, Runtime 272/272, ScriptingEntities
12/12 green.

tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests/Drivers/DeploymentArtifactAliasParityTests.cs

@@ -178,7 +178,7 @@ public sealed class DeploymentArtifactAliasParityTests
 
     /// <summary>
     ///     The load-bearing direct byte-parity proof for the two equipment-tag producers: for the SAME
-    ///     input draft, the live-edit composer (<see cref="Phase7Composer.Compose"/>) and the
+    ///     input draft, the live-edit composer (<see cref="AddressSpaceComposer.Compose"/>) and the
     ///     artifact decoder (<see cref="DeploymentArtifact.ParseComposition(System.ReadOnlySpan{byte})"/>)
     ///     must emit IDENTICAL <c>EquipmentTags</c> — element-wise equal on every field
     ///     (TagId, EquipmentId, DriverInstanceId, FolderPath, Name, DataType, FullName) AND in the same
@@ -275,7 +275,7 @@ public sealed class DeploymentArtifactAliasParityTests
         var namespaces = new[] { ns };
 
         // ---- Side 1: the live-edit composer ----
-        var composed = Phase7Composer.Compose(
+        var composed = AddressSpaceComposer.Compose(
             areas, lines, equipment, drivers, Array.Empty<ScriptedAlarm>(), tags, namespaces);
 
         // ---- Side 2: serialise the SAME draft to the artifact blob shape ConfigComposer emits
@@ -349,7 +349,7 @@ public sealed class DeploymentArtifactAliasParityTests
     ///     The native-alarm <c>historizeToAveva</c> opt-out (bool?, the per-condition durable-AVEVA-write
     ///     gate) is parsed by BOTH equipment-tag producers' <c>ExtractTagAlarm</c> and MUST stay byte-parity:
     ///     for the SAME tag TagConfig carrying <c>alarm.historizeToAveva: true</c> (and <c>: false</c>), the
-    ///     live-edit composer (<see cref="Phase7Composer.Compose"/>) and the artifact decoder
+    ///     live-edit composer (<see cref="AddressSpaceComposer.Compose"/>) and the artifact decoder
     ///     (<see cref="DeploymentArtifact.ParseComposition(System.ReadOnlySpan{byte})"/>) must derive the
     ///     identical <c>EquipmentTagAlarmInfo.HistorizeToAveva</c>. The galaxy-tag parity test above already
     ///     covers the absent ⇒ null case; this pins the explicit-bool branch on both sides.
@@ -399,7 +399,7 @@ public sealed class DeploymentArtifactAliasParityTests
         };
 
         // ---- Side 1: the live-edit composer ----
-        var composed = Phase7Composer.Compose(
+        var composed = AddressSpaceComposer.Compose(
             new[] { area }, new[] { line }, new[] { equip }, new[] { driver },
             Array.Empty<ScriptedAlarm>(), new[] { alarmTag }, new[] { ns });