[ENH]: Local Observability Stack with OTEL and Zipkin

[tazarov]

Description of changes

Summarize the changes made by this PR.

• New functionality
  • Added the possibility to run the observability stack (OTEL collector + Zipkin) alongside Chroma server in a docker-compose

Test plan

How are these changes tested?

• Manual testing

Documentation Changes

Observability section on chroma docs updated - chroma-core/docs#149

[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 (Readbility, Modularity, Intuitiveness)

[HammadB]

Should we add docs about this example to docs.trychroma.com?

[HammadB]

Woops

[tazarov]

@HammadB, I'm fine with that. Here https://docs.trychroma.com/observability, right?

[tazarov]

Done

[tazarov]

@HammadB, I think you can rerun the failed tests then we this + docs PR should be ready to merge.

[tazarov]

@HammadB, this is ready for merge.

[beggers]

Noice