libsql-server: expect resumed drain attribution after restart

Co-authored-by: Tomasz Szymczyszyn <tomasz.szymczyszyn@shopify.com>

Author: shopify-river

libsql-server/src/namespace/fence/tests.rs

@@ -610,7 +610,7 @@ fn restart_at(case: &Boundary) {
                 // The drain that was requested resumes and completes at once: recovery
                 // discarded any uncommitted work. The boundary is on the live, rebuilt log.
                 let commit = replay.unwrap();
-                assert_eq!(commit.kind, FenceCommitKind::Committed, "{name}");
+                assert_eq!(commit.kind, FenceCommitKind::Resumed, "{name}");
                 assert_eq!(commit.receipt.outcome, FenceOutcome::Applied, "{name}");
                 assert_eq!(commit.receipt.command_id, request.command_id);
                 assert_eq!(commit.receipt.revision_after, 2, "{name}");
@@ -1569,10 +1569,10 @@ mod read_and_target_boundaries {
             }
 
             let replay = server.execute(request.clone()).await.unwrap().unwrap();
-            let kind = if case.durable == Durable::Final {
-                FenceCommitKind::Replayed
-            } else {
-                FenceCommitKind::Committed
+            let kind = match case.durable {
+                Durable::Nothing => FenceCommitKind::Committed,
+                Durable::Draining => FenceCommitKind::Resumed,
+                Durable::Final => FenceCommitKind::Replayed,
             };
             assert_eq!(replay.kind, kind, "{name}");
             assert_eq!(replay.receipt.outcome, FenceOutcome::Applied, "{name}");