refactor: replace inline purgatory sync registration with timer-only approach

Remove the redundant inline kind-30617 registration block from the sync
event loop and the three is_generic/recompute_new_sync_filters_for_relay
calls from confirm_batch error paths. The purgatory announcement sync
timer (run_purgatory_announcement_sync) is now the sole registration path.

Consolidate NGIT_SYNC_BATCH_WINDOW_MS and NGIT_PURGATORY_SYNC_INTERVAL_MS
into a single NGIT_TEST=1 flag that sets both timers to 200ms, replacing
two ad-hoc env vars with one reusable test-mode flag.

1 files changed, 1 insertions, 1 deletions

diff --git a/tests/sync/maintainer_reprocessing.rs b/tests/sync/maintainer_reprocessing.rs
index 61d8e14..ff1eb43 100644
--- a/tests/sync/maintainer_reprocessing.rs
+++ b/tests/sync/maintainer_reprocessing.rs
@@ -377,7 +377,7 @@ async fn test_multiple_maintainers_all_reprocessed() {
     println!("relay_b started at {}", relay_b.url());
 
     // Give relay_b's SyncManager time to complete the initial negentropy sync with relay_a.
-    // The negentropy sync completes within ~200ms (NGIT_SYNC_BATCH_WINDOW_MS=200), but we
+    // The negentropy sync completes within ~200ms (NGIT_TEST=1 sets batch window to 200ms), but we
     // allow extra time for slow CI environments.
     tokio::time::sleep(Duration::from_secs(3)).await;
     println!("✓ relay_b synced from relay_a (maintainer announcements should be in hot cache)");