[BUG]: Fix cross version compatibility 0.5.0 or lower with 0.5.1+

[tazarov]

Closes #2377 #2379

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Making dimension and version lookup optional in the Collection model creation in fastapi client

Test plan

How are these changes tested?

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

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)

[tazarov]

• [BUG]: Fix cross version compatibility 0.5.0 or lower with 0.5.1+ #2378 👈
• main

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

Join @tazarov and the rest of your teammates on Graphite

[HammadB]

We don't usually make changes for sake of forward compatibility but this makes sense.

[HammadB]

Don't we have to do this in other methods too - like get_collection?

[HammadB]

What about list_collections?

[HammadB]

What about https://github.com/chroma-core/chroma/blob/main/chromadb/api/async_fastapi.py?

Can we encapsulate this so we aren't repeating it everywhere?

cc @codetheweb

[tazarov]

Done.

[tazarov]

@HammadB, shouldn't dimension and version also make it into chromadb.api.models.CollectionCommon.CollectionCommon, or are these for internal consumption?

[codetheweb]

@HammadB, shouldn't dimension and version also make it into chromadb.api.models.CollectionCommon.CollectionCommon, or are these for internal consumption?

CollectionCommon is just a base class with some helpers that the async/sync variants inherent from. I don't think it needs to care about those fields unless I'm missing something.

[HammadB]

@tazarov

1. That is unrelated to this PR.
2. I don't think we need to expose these right now. We could maybe expose dimension but version is internal.