[BUG] fix multi collection log purge

[codetheweb]

Description of changes

Fixes a bug where if any collection had dangling logs, any logs created after those by other collections would not get purged.

Also fixes a small, somewhat related bug with chroma utils vacuum (see PR comment below).

Test plan

How are these changes tested?

Added a new regression test that was formerly failing.

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]

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)

[codetheweb]

fixes a bug where if trigger_vector_segments_max_seq_id_migration() below attempted to load a segment, it would throw because the SQLite component wasn't technically started
this scenario happens when upgrading from an old version or when any collection had not yet hit its first sync_threshold persist trigger
was not caught because the CLI test didn't add any collections, I updated the test to trigger this path

[codetheweb]

using .get_model().get_configuration() was always returning the default config
not sure if this was due to a recent change because I'm pretty sure it was working correctly when I added it

[codetheweb]

alternative: a new multi-collection state machine that creates records
(this is harder than just modifying the existing multi-collection state machine because invariants can't inspect bundles)

[codetheweb]

Reviewed in person with @HammadB.