feat(centralui): server-side paging + server-computed status counts on Deployments (R3)

The Deployment Status page client-materialized the whole deployment list. It read
EVERY DeploymentRecord — an insert-only table, one row per deploy attempt for the
retention window — plus EVERY Instance, then site-scoped, sorted, counted the four
status tiles and sliced a 25-row page in the Blazor circuit's memory. That ran on
first render AND on every IDeploymentStatusNotifier push, so the cost scaled with
the age of the system rather than the size of the page.

All four jobs move into SQL:

- `IDeploymentManagerRepository.QueryDeploymentListPageAsync(filter, page, size)`
  returns one page of `DeploymentListRow` — DeploymentRecord INNER JOINed to
  Instance, so the instance display name and site travel with the rows that need
  them — plus the total count of the filtered set. The join is exact: the FK is
  Restrict and DeleteInstanceAsync removes the records first, so no orphan exists.
- `GetDeploymentStatusCountsAsync(filter)` returns the tile counts from ONE grouped
  aggregation, deliberately ignoring the filter's Status: the tiles are the status
  BREAKDOWN of the filtered set, so honouring it would zero three of four tiles the
  moment an operator clicked one.
- Site scoping runs in the query as `SiteIdScope` resolved through the record's
  instance (DeploymentRecord has no SiteId of its own). An EMPTY grant stays a real
  filter matching nothing, never "unconstrained".
- The now-callerless whole-table `GetAllDeploymentRecordsAsync` is deleted.

OFFSET paging, not the Audit Log's keyset cursor, and deliberately so: this page's
pager is numbered and jump-to-any-page, so it needs a page count, which only a total
can give it — a keyset cursor can express neither, and the total is required for the
tiles regardless. The deep-offset cost that pushes high-volume tables to keyset is
bounded here by the terminal-record retention purge, unlike the 365-day AuditLog.
This mirrors the Notification Outbox, offset-paged for the same reason. Ordering is
DeployedAt DESC, Id DESC — the Id tie-break is load-bearing, because DeployedAt ties
on rapid redeploys and an unstable sort key makes offset paging repeat or drop rows.

UI: the four status tiles become the status filter (click to apply, click again to
clear, aria-pressed, phrasing-only content so a <button> stays valid), plus a
free-text search matched DB-side against instance name, deployment id, revision hash
and initiating user. Search is TRAILING-edge debounced at 500ms — the same Timer +
lock + _disposed idiom as the existing leading-edge push coalescer, minus the leading
edge, because a search box must not query on the first keystroke. A filter change
resets to page 1; a page past the end falls back to the last real page. Bootstrap
only, existing PagerWindow pager retained.

The WP2.4 push coalescing is unchanged and still earns its keep: server paging shrank
what a reload costs, not how many arrive — it now bounds database round-trips rather
than table scans.

Tests: 19 new SQLite repository tests (paging slice + total, tie-break stability
across pages, page/size clamping, past-the-end, the joined projection, every filter
dimension incl. the empty-scope security case, and the grouped counts' status-blind
contract); 15 new bUnit page tests (page-1 request, server total drives the pager,
Next re-queries, tiles show server counts not page counts, tile filter + toggle,
system-wide vs site-scoped scope push, debounce collapses a keystroke burst to one
query, clear-filters, dispose with an armed timer). The two existing Deployments
suites re-point their reload assertions at the new query.

Doc: Component-CentralUI.md Deployment section — the "no server-side paging" known
residual is replaced by the shipped design.

tests/ZB.MOM.WW.ScadaBridge.CentralUI.Tests/Deployment/DeploymentsPushUpdateTests.cs

@@ -6,9 +6,8 @@ using Microsoft.Extensions.DependencyInjection;
 using Microsoft.Extensions.Logging.Abstractions;
 using NSubstitute;
 using ZB.MOM.WW.ScadaBridge.CentralUI.Auth;
-using ZB.MOM.WW.ScadaBridge.Commons.Entities.Deployment;
-using ZB.MOM.WW.ScadaBridge.Commons.Entities.Instances;
 using ZB.MOM.WW.ScadaBridge.Commons.Interfaces.Repositories;
+using ZB.MOM.WW.ScadaBridge.Commons.Types.Deployment;
 using ZB.MOM.WW.ScadaBridge.Commons.Types.Enums;
 using ZB.MOM.WW.ScadaBridge.DeploymentManager;
 using DeploymentsPage = ZB.MOM.WW.ScadaBridge.CentralUI.Components.Pages.Deployment.Deployments;
@@ -23,29 +22,32 @@ namespace ZB.MOM.WW.ScadaBridge.CentralUI.Tests.Deployment;
 /// the timer and subscribes to <see cref="IDeploymentStatusNotifier"/>, which
 /// <c>DeploymentService</c> raises on every deployment-record status write;
 /// Blazor Server then pushes the re-render over its SignalR circuit.
+///
+/// <para>
+/// The "did it reload?" assertions moved from <c>GetAllDeploymentRecordsAsync</c>
+/// to <c>QueryDeploymentListPageAsync</c> when the page's read path went
+/// server-paged (residual R3) — the push mechanism under test is unchanged, only
+/// the query it drives.
+/// </para>
 /// </summary>
 public class DeploymentsPushUpdateTests : BunitContext
 {
     private IDeploymentManagerRepository _deployRepo = null!;
-    private ITemplateEngineRepository _templateRepo = null!;
     private DeploymentStatusNotifier _notifier = null!;
 
     private void RegisterServices()
     {
         _deployRepo = Substitute.For<IDeploymentManagerRepository>();
-        _templateRepo = Substitute.For<ITemplateEngineRepository>();
         _notifier = new DeploymentStatusNotifier(NullLogger<DeploymentStatusNotifier>.Instance);
 
-        _templateRepo.GetAllInstancesAsync(Arg.Any<CancellationToken>())
-            .Returns(new List<Instance>
-            {
-                new("Inst-1") { Id = 1, SiteId = 1 }
-            });
-        _deployRepo.GetAllDeploymentRecordsAsync(Arg.Any<CancellationToken>())
-            .Returns(new List<DeploymentRecord>());
+        _deployRepo.QueryDeploymentListPageAsync(
+                Arg.Any<DeploymentListFilter>(), Arg.Any<int>(), Arg.Any<int>(), Arg.Any<CancellationToken>())
+            .Returns(DeploymentListPage.Empty);
+        _deployRepo.GetDeploymentStatusCountsAsync(
+                Arg.Any<DeploymentListFilter>(), Arg.Any<CancellationToken>())
+            .Returns(DeploymentStatusCounts.Empty);
 
         Services.AddSingleton(_deployRepo);
-        Services.AddSingleton(_templateRepo);
         Services.AddSingleton<IDeploymentStatusNotifier>(_notifier);
 
         var identity = new ClaimsIdentity(
@@ -80,9 +82,8 @@ public class DeploymentsPushUpdateTests : BunitContext
         RegisterServices();
         var cut = Render<DeploymentsPage>();
 
-        // Initial load: instances + records each fetched once.
+        // Initial load: the paged query is issued once.
         _deployRepo.ClearReceivedCalls();
-        _templateRepo.ClearReceivedCalls();
 
         // A deployment status write in DeploymentManager raises the notifier;
         // the page must reload in response (no polling timer involved).
@@ -90,7 +91,8 @@ public class DeploymentsPushUpdateTests : BunitContext
             new DeploymentStatusChange("dep-1", 1, DeploymentStatus.Success));
 
         cut.WaitForAssertion(() =>
-            _deployRepo.Received().GetAllDeploymentRecordsAsync(Arg.Any<CancellationToken>()));
+            _deployRepo.Received().QueryDeploymentListPageAsync(
+                Arg.Any<DeploymentListFilter>(), Arg.Any<int>(), Arg.Any<int>(), Arg.Any<CancellationToken>()));
     }
 
     [Fact]
@@ -106,8 +108,8 @@ public class DeploymentsPushUpdateTests : BunitContext
         _notifier.NotifyStatusChanged(
             new DeploymentStatusChange("dep-2", 1, DeploymentStatus.Failed));
 
-        _deployRepo.DidNotReceive()
-            .GetAllDeploymentRecordsAsync(Arg.Any<CancellationToken>());
+        _deployRepo.DidNotReceive().QueryDeploymentListPageAsync(
+            Arg.Any<DeploymentListFilter>(), Arg.Any<int>(), Arg.Any<int>(), Arg.Any<CancellationToken>());
     }
 
     /// <summary>
@@ -150,7 +152,7 @@ public class DeploymentsPushUpdateTests : BunitContext
 
         Assert.Null(ex);
         // The guard short-circuits before any reload is attempted.
-        _deployRepo.DidNotReceive()
-            .GetAllDeploymentRecordsAsync(Arg.Any<CancellationToken>());
+        _deployRepo.DidNotReceive().QueryDeploymentListPageAsync(
+            Arg.Any<DeploymentListFilter>(), Arg.Any<int>(), Arg.Any<int>(), Arg.Any<CancellationToken>());
     }
 }