[ENH] Support delayed workloads in chroma-load-start.

[rescrv]

No description provided.

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

[Sicheng-Pan]

Lgtm. I'm wondering if it's worth it to add an auxiliary argument so that the delay can be calculated based on a offset to current time (instead of directly specifying the start timestamp like this)

[rescrv]

Like's done in the humanize_expires time? https://github.com/chroma-core/chroma/blob/main/rust/load/src/lib.rs#L1428

[Sicheng-Pan]

Like's done in the humanize_expires time? https://github.com/chroma-core/chroma/blob/main/rust/load/src/lib.rs#L1428

That would be good