[ENH] Implement `MetadataProvider`, `RoaringMetadataFilter`, and refactor `MetadataFilteringOperator`

[Sicheng-Pan]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Refactors the MetadataFilteringOperator. Now it should produce the exact set of offset ids that should be contained in the result, so that the next operator can only focus on hydrating the offset ids.
• New functionality
  • Implement the MetadataProvider enum, which represents an universal interface for metadata access. Currently it can be constructed either from materialized logs or a MetadataSegmentReader.
  • Introduce the RoaringMetadataFilter trait, which helps to evaluate a Where clause given a MetadataProvider. $ne and $nin are supported as part of this process

Test plan

How are these changes tested?

This is guaranteed to break existing tests. Only the last PR in the stack addresses the breaking changes, and should pass the existing tests. In particular, any test involving the query node should fail because of compilation errors.

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

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

N/A

[github-actions[bot]]

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)

[Sicheng-Pan]

• #2849
• #2848
• #2847 👈
• #2846
• main

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

Join @Sicheng-Pan and the rest of your teammates on Graphite

[Sicheng-Pan]

Merge activity

• Sep 30, 7:32 PM EDT: @Sicheng-Pan started a stack merge that includes this pull request via Graphite.
• Sep 30, 7:34 PM EDT: Graphite rebased this pull request as part of a merge.
• Sep 30, 7:35 PM EDT: @Sicheng-Pan merged this pull request with Graphite.