fix(db): update ru history indices instead of using the host block number

This will cause issues since we're not providing the correct number for changeset updates on the L2.

Author: Evalir

crates/db/src/provider.rs

@@ -470,7 +470,7 @@ where
             index += 1;
         }
 
-        self.update_history_indices(host_height..=host_height)?;
+        self.update_history_indices(ru_height..=ru_height)?;
 
         self.update_pipeline_stages(ru_height, false)?;