Fix flaky WAL filter-resolution test by disabling aggressive flush (#10446)

The test asserts live WAL contents after applied updates, but the default
fixture uses flush_interval_sec = 0 so the flush worker can truncate
earlier rewritten records before the assertion runs.

Fixes #10423

lib/collection/src/tests/wal_recovery_test.rs

@@ -1183,7 +1183,11 @@ async fn test_filter_ops_resolved_to_ids_in_wal() {
     let _ = env_logger::builder().is_test(true).try_init();
     let collection_dir = Builder::new().prefix("test_collection").tempdir().unwrap();
 
-    let config = create_collection_config();
+    // This test inspects live WAL contents after applied updates. The default
+    // fixture uses `flush_interval_sec = 0`, so the flush worker can ack and
+    // truncate earlier records before we read them (issue #10423).
+    let mut config = create_collection_config();
+    config.optimizer_config.flush_interval_sec = 3600;
     let collection_name = "test".to_string();
 
     let update_runtime = Handle::current();