add some debug logs to check my hypothesis: when the buffer reader is…

… initialized and then catches up to the writer, it waits for the writer to notify it (but the writer will never write more data in the vector buffer recovery topology/pipeline)

lib/vector-buffers/src/variants/disk_v2/reader.rs

@@ -977,6 +977,7 @@ where
             if self.ledger.is_writer_done() {
                 let total_buffer_size = self.ledger.get_total_buffer_size();
                 if total_buffer_size == 0 {
+                    debug!("writer is done and total buffer size is 0");
                     return Ok(None);
                 }
             }
@@ -1074,6 +1075,7 @@ where
                     continue;
                 }
 
+                debug!("reader is on writer's current data file: waiting for writer to wake the reader");
                 self.ledger.wait_for_writer().await;
             } else {
                 debug!(