feat(cli,management): close area-move and template-folder CLI parity gaps

Two verified-absent parity gaps between the service layer and the CLI /
ManagementActor command surface, both left as follow-ups by the 2026-05-11
design plans.

(1) area move. AreaService.MoveAreaAsync had existed since the deployment
topology page shipped but was reachable only from the Blazor UI. Adds
MoveAreaCommand(AreaId, NewParentAreaId?) to Commons, a ManagementActor
dispatch arm delegating straight to AreaService.MoveAreaAsync (not-found /
self-parent / descendant-cycle / cross-site / name-collision all surface as
the standard curated ManagementCommandException failure response; the service
writes its own "Move" audit row), and the CLI verb `site area move --id
[--parent-id]`. Omitting --parent-id moves the area to the site root, matching
the command's nullable NewParentAreaId. The command carries the SAME any-of
[Designer, Deployer] gate as CreateArea/UpdateArea/DeleteArea (arch-review C6):
re-parenting is the same structural authoring act, exposed on the same two
surfaces. Placed under the existing `site area` group rather than a new
top-level `area` group, alongside its create/update/delete siblings.

(2) template folder verbs. The five folder management commands have been
handled by ManagementActor since the folder-hierarchy plan, but the promised
CLI surface was never written. Adds `template folder
list|create|rename|move|reorder|delete` mapping 1:1 onto ListTemplateFolders /
CreateTemplateFolder / RenameTemplateFolder / MoveTemplateFolder /
ReorderTemplateFolder / DeleteTemplateFolder. --parent-id is omitted to target
the tree root; --direction takes the lowercase literals up/down, validated at
parse time by AcceptOnlyFromAmong (same case-sensitive contract as the audit
--channel/--kind/--status options).

Follow-on updates: the frozen authorization matrix gains its MoveArea entry
(reflection-driven, so a missing entry would have failed CI); CommandTreeTests
pins both new verb sets plus the omit-parent-id-means-root parse behaviour and
registry round-trips; ManagementActorTests covers the MoveArea role gate and
the delegate-to-service success/root/cycle/not-found paths; the CLI README and
Component-ManagementService.md document the new surface (the latter also gained
the previously-undocumented ReorderTemplateFolder); both plan docs' follow-up
lines are marked done.

src/ZB.MOM.WW.ScadaBridge.CLI/Commands/SiteCommands.cs

@@ -183,6 +183,23 @@ public static class SiteCommands
         });
         group.Add(updateCmd);
 
+        // Omitting --parent-id moves the area to the site root, matching
+        // AreaService.MoveAreaAsync's null newParentAreaId contract.
+        var moveIdOption = new Option<int>("--id") { Description = "Area ID", Required = true };
+        var moveParentOption = new Option<int?>("--parent-id") { Description = "New parent area ID; omit to move to the site root" };
+        var moveCmd = new Command("move") { Description = "Move an area under a new parent area (or to the site root)" };
+        moveCmd.Add(moveIdOption);
+        moveCmd.Add(moveParentOption);
+        moveCmd.SetAction(async (ParseResult result) =>
+        {
+            var id = result.GetValue(moveIdOption);
+            var parentId = result.GetValue(moveParentOption);
+            return await CommandHelpers.ExecuteCommandAsync(
+                result, urlOption, formatOption, usernameOption, passwordOption,
+                new MoveAreaCommand(id, parentId));
+        });
+        group.Add(moveCmd);
+
         var deleteIdOption = new Option<int>("--id") { Description = "Area ID", Required = true };
         var deleteCmd = new Command("delete") { Description = "Delete an area" };
         deleteCmd.Add(deleteIdOption);