[BUG]: Don't log offset since records can be empty (#5812)

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
- There was a tracing in RLS where records[0] was printed
unconditionally. However, records can be empty so records[0] goes out of
bound causing a panic during pull logs. Fixed by not tracing it
- New functionality
  - ...

## Test plan

_How are these changes tested?_
- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Migration plan
None

## Observability plan
None

## Documentation Changes
None

Author: sanketkedia

rust/log-service/src/lib.rs

@@ -1388,10 +1388,7 @@ impl LogServer {
         if records.len() != pull_logs.batch_size as usize
             || (!records.is_empty() && records[0].log_offset != pull_logs.start_from_offset)
         {
-            return Err(Status::not_found(format!(
-                "Some entries have been purged {} versus {}",
-                records[0].log_offset, pull_logs.start_from_offset
-            )));
+            return Err(Status::not_found("Some entries have been purged"));
         }
         Ok(Response::new(PullLogsResponse { records }))
     }