[ENH]: make S3 tracing spans less verbose by default

[codetheweb]

Description of changes

Bumps the tracing level of chroma-storage to debug from trace.

I audited all spans in rust/storage to ensure all high-frequency code paths only have trace-level events and that any errors are correctly logged with the error level.

Test plan

How are these changes tested?

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

Confirmed that S3 spans no longer show up in Jaeger.

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)

[propel-code-bot]

This PR reduces the default verbosity of S3-related tracing by raising the minimum log level for chroma-storage from trace to debug in the tracing filter and by downgrading several S3 operation log messages (info → debug or removal). Adjustments are made in the storage and tracing modules to ensure high-frequency code paths no longer produce excessive span events, with error-level logs retained for failures.

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