[ENH] Fix issues + add sync point to test embeddings

[sanketkedia]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Fixes allowed_ids and disallowed_ids to also take care of updates/deletes/upserts. For e.g. if there is an update on the log that does not update the embedding and it is in the query list then today we are never going to return this record even if it is in the top k
  • Adds sync points to test_embeddings + increase test timeout
  • Adds another rule in test_embeddings for compaction
  • Suppresses health check warning for filtering too much
  • Fixes the case when trying to commit and flush an empty block (can happen due to deletes). Sparse index start key can also get changed to something that is not SparseIndexDelimiter::Start. We decided to go ahead with flushing a dummy block if blockfile becomes fully empty so that our segment abstraction is only uninitialized until the first compaction; post that it is always initialized albeit with empty block
  • Fixes a bug in FTS delete document where we were incorrectly panicing
  • Fixes a bug in record segment apply materialization where for deletes and updates we missed writing the max offset id
  • Updates to metadata segment were missing updating the document and were only updating the metadata
  • Don't return error from the metadata segment if document is supplied as None for an update

Test plan

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

Documentation Changes

None

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

[HammadB]

would love to grab 5 minutes just to make sure I understand the logic changes in hnsw_knn.rs

[HammadB]

looks good minus comments around mixin and the blockfile changes