fmt: rustfmt budgets macro arguments at 60 chars, not the 100-char line

Both new assertions fit well inside the 100-column limit and both were still
rejected. The governing setting is `fn_call_width` (60), applied to a macro's
argument list: `survivor.id, older.id, "the older row is the one that
survives"` is 62 characters, so rustfmt breaks it and pairs the two values on
one line with the message beneath.

The neighbouring `assert_eq!(survivor.name, "Grocery", "spelled the way the
caller asked")` was accepted at 59 characters of arguments, which is the
same rule agreeing rather than a different one.

rustfmt's own output, pasted back. Second time this lane has caught the same
class of thing in one session — the other was a method chain, budgeted at 60
by `chain_width`. Recorded so the next person reaches for the 60, not the 100.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K3MMqUtzX1TJgA1oypvm1c

android/ffi/src/lib.rs

@@ -996,7 +996,10 @@ mod tests {
             .rename_label(newer.id.clone(), "Grocery".to_string())
             .expect("a rename onto an existing name merges instead of failing");
 
-        assert_eq!(survivor.id, older.id, "the older row is the one that survives");
+        assert_eq!(
+            survivor.id, older.id,
+            "the older row is the one that survives"
+        );
         assert_eq!(survivor.name, "Grocery", "spelled the way the caller asked");
 
         let all = app.list_labels().expect("list");
@@ -1028,7 +1031,10 @@ mod tests {
 
         assert_eq!(survivor.id, older.id, "age wins in this direction too");
         assert_eq!(survivor.name, "errands");
-        assert_ne!(survivor.id, newer.id, "the younger row is the one that went");
+        assert_ne!(
+            survivor.id, newer.id,
+            "the younger row is the one that went"
+        );
         assert_eq!(app.list_labels().expect("list").len(), 1);
 
         std::fs::remove_dir_all(&dir).ok();