[ENH] A tool to inspect the number of records on the log.

[rescrv]

Description of changes

I added a gauge that floats the number of collections uncompacted and
extended the inspect-log-state route to have return the start/limit and
number of records on the log.

Test plan

CI

Documentation Changes

Will update runbooks.

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

This PR extends the log inspection tooling and API by enriching the InspectLogStateResponse with start and limit fields, enabling direct calculation and reporting of the number of records in a log. The CLI tool chroma-inspect-log-state now displays these additional fields and the record count, while the Rust log service and proto definition are updated accordingly.

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