Fix/ordering filter mixed str datetime

[rautaditya2606]

Related Issues

fixes #11678

Proposed Changes

• Update _prepare_ordering_comparison() to only call _parse_date() on operands that are actually strings.
• Normalize naive/aware datetimes via _ensure_both_dates_naive_or_aware() when both operands resolve to datetime.
• Wrap >, >=, <, <= operators in try/except TypeError → FilterError to preserve existing error behavior.
• Added regression tests for aware datetime vs string date and naive datetime vs aware ISO string.
• Added release note.

How did you test it?

hatch run test:unit test/utils/test_filters.py -k document_matches_filter

92 tests passed.

Notes for the reviewer

• Root cause: _prepare_ordering_comparison() called _parse_date() on both operands when either was a string, crashing when the other was already a datetime.
• Mixed string/datetime comparisons are valid — ISO date strings in Document.meta compared against datetime filter values is a real use case.
• TypeError wrapping keeps error behavior consistent with existing Haystack conventions.

Checklist

• Read contributors guidelines and code of conduct
• Updated related issue
• Added unit tests and updated docstrings
• Used conventional commit type in PR title
• Documented code
• Added release note
• Run pre-commit hooks and fixed any issues

[vercel]

@rautaditya2606 is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
haystack/utils
filters.py
Project Total

This report was generated by python-coverage-comment-action