fix(sqlite): bounds-check value_col_indices in push_batch

push_batch validated key_col_index but not value_col_indices; an
out-of-range entry would panic in row_to_params on batch.column(ci)
rather than returning a clean DataFusionError. Validate both, and add a
test for the out-of-range value-index case. Addresses PR review nit.

Author: anoop-narang

src/sqlite_provider.rs

@@ -366,6 +366,11 @@ impl SqliteSidecarBuilder {
                 self.key_col_index
             )));
         }
+        if let Some(&bad) = self.value_col_indices.iter().find(|&&i| i >= ncols) {
+            return Err(DataFusionError::Execution(format!(
+                "value column index {bad} out of range for batch with {ncols} columns"
+            )));
+        }
         let key_col = batch.column(self.key_col_index);
         let mut stmt = self
             .conn

tests/sqlite_provider_test.rs

@@ -254,6 +254,11 @@ fn test_stream_builder_validation_errors() {
     .unwrap();
     assert!(b_oob.push_batch(&two_col).is_err());
 
+    // value_col_index out of range for the pushed batch (clean error, no panic).
+    let mut b_voob =
+        SqliteSidecarBuilder::begin(&db("c2.db"), "t", 1, schema.clone(), 0, vec![9]).unwrap();
+    assert!(b_voob.push_batch(&two_col).is_err());
+
     // A null key value is rejected.
     let nullable = Arc::new(Schema::new(vec![
         Field::new("rowid", DataType::Int64, true),