[ENH] Introduce spann segment reader

[sanketkedia]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Spann segment reader with from_segment impl
• New functionality
  • ...

Test plan

How are these changes tested?

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

Documentation Changes

None

[sanketkedia]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [ENH] Fetch posting list operator #3214
• [ENH] rng_query_operator #3213
• [ENH] Introduce spann segment reader #3212 👈 (View in Graphite)
• [ENH] Full garbage collection #3194
• [ENH] SPANN: Implement update and delete #3185
• [ENH] Implement append #3182
• [ENH] Implement K Means #3159
• [ENH] implement append, commit and flush for spann segment and index #3084
• [ENH] Introduce spann segment and index #3080
• [CLN] Cleanup hnsw provider to not know about segments #3044
• [ENH] BF writer support reads #3031
• [ENH] Add new value type for spann posting lists #3022
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Please tag your PR title with one of: [ENH | BUG | DOC | TST | BLD | PERF | TYP | CLN | CHORE]. See https://docs.trychroma.com/contributing#contributing-code-and-ideas

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