Summary

• Fix check_datetime_range in qdrant_client/local/payload_filters.py to avoid mutating its condition argument in-place.
• Previously, the function reassigned condition.lt, condition.lte, condition.gt, and condition.gte with timezone-aware conversions, permanently altering the caller's DatetimeRange filter object.
• Now uses local variables for the timezone-aware boundaries, leaving the original condition unchanged.

Problem

When check_datetime_range is called with a DatetimeRange condition containing timezone-naive datetime or date boundaries, it converts them to timezone-aware datetime objects directly on the condition object (lines 138-141). This has two side effects:

1. Type mutation: date objects on the condition are silently converted to datetime objects, which could break downstream code that inspects the filter type.
2. Persistent modification: The caller's filter object is permanently altered. While this is idempotent for subsequent calls (already-converted values are unchanged), it violates the expectation that a predicate function (check_*) should not modify its inputs.

Fix

Use local variables (lt, lte, gt, gte) instead of reassigning attributes on the condition object. The comparison logic remains identical.

Test plan

• Existing tests for datetime range filtering should continue to pass.
• Verify that reusing a DatetimeRange filter across multiple check_datetime_range calls no longer mutates the filter.