feat(notif): NotificationOutboxActor + CentralAuditWriter wired (#23 M4)

M4 Bundle B (B1) — add the central-only ICentralAuditWriter implementation
and inject it into NotificationOutboxActor so subsequent tasks (B2/B3) can
route attempt + terminal lifecycle events through the direct-write audit path.

- CentralAuditWriter: thin wrapper around IAuditLogRepository.InsertIfNotExistsAsync;
  scope-per-call (matches AuditLogIngestActor / NotificationOutboxActor pattern);
  stamps IngestedAtUtc; swallows all internal failures (alog.md §13).
- Registered as a singleton in AddAuditLog.
- NotificationOutboxActor ctor takes ICentralAuditWriter (validated non-null).
- Host wiring resolves the writer once from the root provider and passes it
  into the singleton's Props.Create call.
- Existing TestKit fixtures updated with a NoOpCentralAuditWriter helper so
  tests that don't exercise audit emission still compile and pass.

tests/ScadaLink.NotificationOutbox.Tests/NotificationOutboxActorQueryTests.cs

@@ -10,6 +10,7 @@ using ScadaLink.Commons.Messages.Notification;
 using ScadaLink.Commons.Types.Enums;
 using ScadaLink.Commons.Types.Notifications;
 using ScadaLink.NotificationOutbox.Delivery;
+using ScadaLink.NotificationOutbox.Tests.TestSupport;
 
 namespace ScadaLink.NotificationOutbox.Tests;
 
@@ -36,6 +37,7 @@ public class NotificationOutboxActorQueryTests : TestKit
             BuildServiceProvider(),
             // A long dispatch interval keeps the dispatch loop from interfering with these tests.
             options ?? new NotificationOutboxOptions { DispatchInterval = TimeSpan.FromHours(1) },
+            new NoOpCentralAuditWriter(),
             NullLogger<NotificationOutboxActor>.Instance)));
     }