[ruff] Fix panic when comments appear between unary operators and operands

[TaKO8Ki]

Summary

Fixes #19226

Fixes a panic in binary expression formatting caused by TextRange assertion failures when comments are positioned between unary operators (like not) and their operands.

The issue occurred because expression.start() points to the unary operator while comment.end() can be positioned after it, creating invalid TextRange where start > end. The fix uses operand.start() for unary operations to ensure proper ordering.

Test Plan

I have added new test cases to crates/ruff_python_formatter/resources/test/fixtures/ruff/expression/unary.py.

[github-actions]

ruff-ecosystem results

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

[MichaReiser]

Thank you. I need to think about whether this is the intended comment placement as it means that a comment can now move "forward" (it moves from after not to before not)

[TaKO8Ki]

@MichaReiser Ok. If it's not intentional, I can make has_lparen_between_comment_and_expression to skip unary.