[pyupgrade] Unwrap unary expressions correctly (UP018)

[InSyncWithFoo]

Summary

Resolves #15859.

The rule now adds parentheses if the original call wraps an unary expression and is:

• The left-hand side of a binary expression where the operator is **.
• The caller of a call expression.
• The subscripted of a subscript expression.
• The object of an attribute access.

The fix will also be marked as unsafe if there are any comments in its range.

Test Plan

cargo nextest run and cargo insta test.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[dscorbett]

Another case to consider is await int(-1).

[MichaReiser]

Could we reuse the Precedence infrastructure introduced in #15762 over implementing the correct precedence manually here?

[InSyncWithFoo]

I'm not sure how to use that OperatorPrecedence to differentiate foo(int(-1)) and int(-1)().

By the way, there are now four OperatorPrecedences around the codebase: two in the formatter, one in the parser and one in the linter.

[MichaReiser]

#16071

[MichaReiser]

Couldn't we use the precedence to represent int's position? I think it's: For the second it's CallAttribute, for the first it's parenthesized (may require adding a new operator precedence)