[ENH]: Support for $in and $nin metadata filters

[tazarov]

Refs: #1105

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • JS Client support for $in and $nin

Test plan

How are these changes tested?

• Tests pass locally yarn test for js

Documentation Changes

TBD

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

[jeffchuber]

this says float, but they are ints?

[tazarov]

I picked up the examples from clients/js/test/data.ts

const METADATAS = [
  { test: "test1", float_value: -2 },
  { test: "test2", float_value: 0 },
  { test: "test3", float_value: 2 },
];

[gururise]

Any possible way to use this in python client?

[tazarov]

@gururise, this was originally implemented for Python and only then came to JS. Check this: https://docs.trychroma.com/usage-guide?lang=py#using-inclusion-operators-in-and-nin