[BUG] Set default client idle timeout

[jasonvigil]

Description of changes

Given a default client timeout of 60s, this sets a much lower value to prevent the client from using "almost timed-out" connections from the pool.

Ref: hyperium/hyper#2136 (comment)

Test plan

ci

Migration plan

n/a

Observability plan

n/a

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]

Set HTTP client pool idle timeout and bump crate versions

Introduces a 30-second pool idle timeout on the reqwest::Client used by ChromaHttpClient to avoid reusing connections that are about to be dropped by servers with 60-second idle limits. Workspace crates (chroma, chroma-api-types, chroma-error, chroma-types) and the root Cargo.toml dependency table receive synchronized version bumps to 0.8.0/0.7.0.

Key Changes

• Imported std::time::Duration and set reqwest::Client::builder().pool_idle_timeout(Duration::from_secs(30)) in rust/chroma/src/client/chroma_http_client.rs with context comments referencing upstream hyper guidance.
• Incremented chroma crate version to 0.8.0 and updated dependent workspace crate versions (chroma-api-types, chroma-error, chroma-types) to 0.7.0 across Cargo.toml files.
• Aligned root workspace dependency entries in Cargo.toml to reference the bumped crate versions.

Affected Areas

• rust/chroma/src/client/chroma_http_client.rs
• Cargo.toml
• rust/chroma/Cargo.toml
• rust/api-types/Cargo.toml
• rust/error/Cargo.toml
• rust/types/Cargo.toml

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

[rescrv]

You'll need to bump the root Cargo.toml as well.

Might I suggest following this and then we can cut a release: https://github.com/chroma-core/hosted-chroma/blob/main/runbooks/publish-chroma-crates.md

[HammadB]

This is fine - I do think a proper keep alive configuration and thought is in order.