[ENH]: add readiness probe for garbage collector

[codetheweb]

Description of changes

Adds a readiness probe for GC.

Test plan

How are these changes tested?

Verified that the service was marked ready using kubectl.

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?
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)

[github-actions]

✅ The Helm chart's version was changed. Your changes to the chart will be published upon merge to main.

[propel-code-bot]

Add Readiness Probe to Garbage Collector Service

This PR introduces a readiness probe to the garbage collector component in the Chroma distributed system, enabling Kubernetes to verify when the garbage collector service is ready to accept traffic. The implementation involves adding a minimal gRPC health service and configuring the Helm and k8s manifests accordingly, with corresponding updates to Rust, proto, and configuration code.

Key Changes:
• Added a gRPC health/readiness probe to the garbage collector by implementing a minimal service in Rust and exposing a corresponding health endpoint.
• Updated Kubernetes Helm chart and garbage-collector YAML to specify a readinessProbe using gRPC on port 50055.
• Created a new proto definition for the (placeholder) garbage_collector service and updated Rust proto generation accordingly.
• Extended garbage collector configuration to support the probe port.
• Added tonic-health as a dependency and updated the Rust service entrypoint to start the health server in parallel to the main service logic.

Affected Areas:
• garbage_collector Rust crate (src/lib.rs, config.rs, garbage_collector_component.rs)
• Kubernetes manifests (k8s/distributed-chroma/templates/garbage-collector.yaml, Chart.yaml)
• Protobuf definitions (idl/chromadb/proto/garbage_collector.proto, rust/types/build.rs, rust/types/src/lib.rs)
• Cargo manifest (rust/garbage_collector/Cargo.toml)
• Cargo.lock

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

[codetheweb]

this is needed to ignore a new warning in the prost-genenerated code--happens because we have a service with no methods and prost generates slightly unidiomatic code