refactor(deployments): one paged read of DeploymentRecords + close its three drifts

Deferred-work register rows 37, 86, 87, 88 — the structural duplication and the
three behavioral divergences it had accumulated, fixed together.

Row 37 (structural). `IDeploymentManagerRepository.QueryDeploymentSummariesAsync`
is DELETED. It and `QueryDeploymentListPageAsync` were two paged reads of the same
insert-only table with different contracts — raw offset vs page number, no total vs
total, no instance join vs joined, instance-id-list scoping vs site-id scoping. The
CLI/HTTP `QueryDeployments` handler now goes through `QueryDeploymentListPageAsync`
with a `DeploymentListFilter`, exactly like the Central UI page. The
`DeploymentRecordSummary` projection went with it (`DeploymentListRow` is the single
row shape); its `MaxPageSize` const moved to `DeploymentListPage`, which also gains
`DefaultPageSize`.

Row 86 (Medium, authorization — the headline). `SiteScopeService.ResolveAsync` was
claims-only, so an Administrator carrying `SiteId` claims saw the whole fleet through
the CLI (`ManagementActor.EnforceSiteScope` has always exempted Administrator) and
only their granted sites on the Deployments page. One user, one dataset, two answers.
Administrator = system-wide is the intended semantic on both sides; the UI was the
defect. The role claim is read explicitly with an OrdinalIgnoreCase comparison rather
than via `IsInRole`, which compares claim VALUES ordinally and only resolves when the
identity carries the matching roleType — the two sides must not disagree on a
differently-cased role name. An Administrator's site claims are not collected at all,
so the invariant "system-wide => empty permitted-id set" holds for every caller.
Designer is NOT exempt: the class doc claimed "any Admin/Design user" is system-wide,
which was true of neither side, so the doc was corrected rather than the bypass
widened.

Row 87 (Low). The scoped branch used to resolve the site grant into an instance-id
list by loading EVERY instance in the system, non-transactionally, on every scoped
query; the grant now rides as `SiteIdScope` and is resolved by the query's own join.
An unparseable permitted-site id is DROPPED, never ignored — dropping can only narrow
a grant, discarding it would widen it to fleet-wide. And `PageSize <= 0` no longer
means UNLIMITED down at the repository (`--page-size 0` materialized the whole
retention window): it means "unspecified" and takes the CLI's own default of 50,
capped at 1000. Bounding without telling would be silent truncation, so the handler
now returns a `DeploymentQueryResult` envelope carrying `totalCount` plus the page
coordinates actually applied — with a CLI table projection (mirroring row 57's
`AuditConfigTableProjection`) that unwraps it and appends a "showing N of M" note.

Row 88 (Low, UX). An unrecognised `--status` fell back to "no filter", so a typo like
`--status Sucess` returned every status — a complete-looking answer to a question the
caller never asked. It is now a `ManagementError` naming the valid values. Parsing
stays case-insensitive; a numeric string is rejected too, since `Enum.TryParse`
accepts "7" and yields an undefined value (guarded with `Enum.IsDefined`). Loud
failure over silent full results, per row 46.

Tests: 7 new `SiteScopeServiceTests` pinning Administrator = system-wide (verified
failing 6/7 against the pre-fix service, the Designer pin passing both ways); the
ManagementActor deployment suite migrated onto the consolidated query with new pins
for the status error, case-insensitive parse, numeric rejection, page-size default/
cap/floor, empty-scope-on-garbage-grant, and "reads no instances at all"; a repository
test for site-scope+status composing over a bounded page; and 6 CLI tests for the new
table projection.

src/ZB.MOM.WW.ScadaBridge.Commons/Interfaces/Repositories/IDeploymentManagerRepository.cs

@@ -16,8 +16,21 @@ public interface IDeploymentManagerRepository
     /// <returns>The deployment record, or null if not found.</returns>
     Task<DeploymentRecord?> GetDeploymentRecordByIdAsync(int id, CancellationToken cancellationToken = default);
     /// <summary>
-    /// Database-side paged, filtered and instance-joined deployment listing —
-    /// the read path behind the Central UI deployment-status page.
+    /// Database-side paged, filtered and instance-joined deployment listing — THE
+    /// paged read of <c>DeploymentRecords</c>, shared by the Central UI
+    /// deployment-status page and the CLI/HTTP <c>QueryDeployments</c> command.
+    ///
+    /// <para>
+    /// It was two reads until deferred-work register row 37. The other one
+    /// (<c>QueryDeploymentSummariesAsync</c>) differed in three ways that were all
+    /// defects rather than requirements: it took a raw <c>skip</c> instead of a page
+    /// number, returned no total (so a truncated page was indistinguishable from a
+    /// complete one), skipped the <c>Instance</c> join, and scoped by a caller-resolved
+    /// INSTANCE-ID LIST — which its one caller built by loading every instance in the
+    /// system on every scoped query. Site scoping is expressed here as
+    /// <see cref="Types.Deployment.DeploymentListFilter.SiteIdScope"/> and resolved by
+    /// the join, so no caller needs that read.
+    /// </para>
     ///
     /// <para>
     /// Replaces a <c>GetAllDeploymentRecords</c> whole-table read. That method's only
@@ -50,7 +63,7 @@ public interface IDeploymentManagerRepository
     /// </summary>
     /// <param name="filter">Status / search / site-scope / instance constraints; all applied DB-side.</param>
     /// <param name="pageNumber">1-based page number; values below 1 are floored at 1.</param>
-    /// <param name="pageSize">Rows per page; clamped to <c>[1, DeploymentRecordSummary.MaxPageSize]</c>.</param>
+    /// <param name="pageSize">Rows per page; clamped to <c>[1, DeploymentListPage.MaxPageSize]</c>. There is no "unlimited" value.</param>
     /// <param name="cancellationToken">A cancellation token that can be used to cancel the operation.</param>
     /// <returns>The requested page of rows plus the total count of the filtered set.</returns>
     Task<Types.Deployment.DeploymentListPage> QueryDeploymentListPageAsync(
@@ -80,31 +93,6 @@ public interface IDeploymentManagerRepository
         Types.Deployment.DeploymentListFilter filter,
         CancellationToken cancellationToken = default);
     /// <summary>
-    /// Database-side paged and filtered deployment query returning row summaries.
-    /// Backs the <c>QueryDeployments</c> management command, which previously
-    /// loaded the ENTIRE deployment-record table (insert-only, one row per deploy
-    /// attempt for the life of the system) and ignored the page arguments the CLI
-    /// was already sending.
-    /// </summary>
-    /// <param name="instanceId">Restrict to one instance's history, or <see langword="null"/> for all.</param>
-    /// <param name="status">Restrict to one deployment status, or <see langword="null"/> for all.</param>
-    /// <param name="instanceIdScope">
-    /// When non-null, restrict to these instance ids. Used to apply a site-scoped
-    /// user's permitted-site filter IN THE DATABASE rather than by loading every
-    /// record and every instance and filtering in memory.
-    /// </param>
-    /// <param name="skip">Rows to skip; negative values are floored at 0.</param>
-    /// <param name="take">Page size; non-positive or null returns every remaining row.</param>
-    /// <param name="cancellationToken">A cancellation token that can be used to cancel the operation.</param>
-    /// <returns>One page of deployment summaries, newest first.</returns>
-    Task<IReadOnlyList<Types.Deployment.DeploymentRecordSummary>> QueryDeploymentSummariesAsync(
-        int? instanceId,
-        DeploymentStatus? status,
-        IReadOnlyCollection<int>? instanceIdScope,
-        int skip,
-        int? take,
-        CancellationToken cancellationToken = default);
-    /// <summary>
     /// Deletes TERMINAL deployment records (<see cref="DeploymentStatus.Success"/> /
     /// <see cref="DeploymentStatus.Failed"/>) that completed before
     /// <paramref name="cutoffUtc"/>, in one bounded batch.