[CLN] Warn on log pull failure instead of error

[HammadB]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • There are valid cases for this log pull to fail, it is not an invariant violation as stated.
  • If the log is failed to be updated with the latest compaction offset (Which is best-effort), but the sysdb was, the log may schedule a collection for compaction that has no records outstanding. This leads to hitting this case, which is valid. In the future we could repair the log.
  • Forked collections will also run into this as the fork() call may copy the old log offset, but a compaction happens after, this leads to them disagreeing but progression is always forward, it manifests as the same issue above which is that the log is behind the sysdb.
  • Keeping this as a warn because its worth monitoring this as it implies log service may be failing to get updated. Or that the fork race is commonly copying unnecessary data.
• New functionality
  • None

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

None

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)