[ENH] When the log offset is behind sysdb, this can repair it safely.

[rescrv]

Description of changes

This adds a tool to make the log offset match sysdb. Then a test to make sure it cannot move things
backwards breaking invariants.

Test plan

Added a test.

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

Documentation Changes

N/A

[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)

[propel-code-bot]

Add Log Offset Repair Tool and Make CheckCollections Return Log Offset

This PR introduces a new Rust command-line tool for safely repairing log offsets by synchronizing them with sysdb, preventing log offsets from being moved backwards and thereby preserving invariants. It also updates the system to return the log offset in sysdb's CheckCollections gRPC/proto API, adds supporting plumbing to Go and Rust code (including new test coverage), and provides a test ensuring offsets never regress.

Key Changes:
• New Rust tool (chroma-update-collection-log-offset.rs) to synchronize log-service log offsets with sysdb for a given collection
• CheckCollectionsResponse in protobuf API now returns both deleted status and log_position for each collection
• Go sysdb table_catalog, coordinator, and grpc layers updated to propagate and respect log_position values
• Integration and error handling updates to ensure deleted or abnormal collections are not processed
• Comprehensive Rust test added to verify update_collection_log_offset logic never moves offsets backwards

Affected Areas:
• Rust log-service (bin and lib)
• Go sysdb coordinator, grpc server, and table_catalog
• IDL protobuf definitions for sysdb/CheckCollections
• Testing for log-service

This summary was automatically generated by @propel-code-bot

[Sicheng-Pan]

nit: "deleted collection"?