chore: info -> debug logging (#4484)

I think INFO level is a bit aggressive for some of these.

<img width="1728" height="513" alt="image"
src="https://github.com/user-attachments/assets/0265c3bf-166d-454a-b28b-f04b3d8ab394"
/>

Signed-off-by: Andrew Duffy <[email protected]>

Author: a10y

vortex-array/src/arrays/primitive/compute/pipeline.rs

@@ -4,7 +4,7 @@
 use std::any::Any;
 use std::sync::Arc;
 
-use log::info;
+use log;
 use vortex_buffer::{Buffer, ByteBuffer};
 use vortex_dtype::{NativePType, PType, match_each_native_ptype};
 use vortex_error::VortexResult;
@@ -19,7 +19,9 @@ use crate::vtable::ValidityHelper;
 impl PipelineVTable<PrimitiveVTable> for PrimitiveVTable {
     fn to_operator(array: &PrimitiveArray) -> VortexResult<Option<OperatorRef>> {
         if !array.validity().all_valid() {
-            info!("PipelineVTable::to_operator is not supported for arrays with invalid values");
+            log::debug!(
+                "PipelineVTable::to_operator is not supported for arrays with invalid values"
+            );
             return Ok(None);
         }
         Ok(Some(Arc::new(PrimitiveOperator::new(

vortex-file/src/generic.rs

@@ -192,7 +192,7 @@ impl VortexOpenOptions<GenericVortexFile> {
 
         // Read more bytes if necessary.
         if read_more_offset < initial_offset {
-            log::info!(
+            log::debug!(
                 "Initial read from {initial_offset} did not cover all footer segments, reading from {read_more_offset}"
             );