fix: remove duplicate length-consistency check from validate_insert_record_set

[bbuklov]

The length consistency check (_validate_record_set_length_consistency) was already performed inside validate_base_record_set, so calling _validate_record_set_length_consistency inside validate_insert_record_set right before the validate_base_record_set call caused redundant validation.
This change removes the duplicate call from validate_insert_record_set to avoid unnecessary work, as the function _validate_record_set_length_consistency does not mutate the global state.

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

[propel-code-bot]

Remove Duplicate Length-Consistency Check in validate_insert_record_set

This pull request eliminates a redundant invocation of the _validate_record_set_length_consistency function from the validate_insert_record_set function in chromadb/api/types.py. The length-consistency check was already being executed within validate_base_record_set, which is called immediately after; thus, the removed line did not serve any additional validation purpose.

Key Changes

• Removed redundant call to _validate_record_set_length_consistency from validate_insert_record_set in chromadb/api/types.py
• validate_base_record_set continues to perform the required consistency check

Affected Areas

• validate_insert_record_set function in chromadb/api/types.py

This summary was automatically generated by @propel-code-bot