Fix Issue 13919: Translation error using negative

[jonlouie]

This pull request resolves Issue #13919: Translation error using negative.

Summary of Issue

If a LINQ query references an entity property and uses a negated expression, negation only applies to the first term in the expression.

Example:
db.Entities.Where(e => e.Num1 == -(e.Num2 + 100))
Expected translation:
SELECT ... FROM Entities e WHERE e.Num1 = -(e.Num2 + 100)
Actual translation:
SELECT ... FROM Entities e WHERE e.Num1 = -e.Num2 + 100

---

Summary of Changes

• On translation, add opening and closing parentheses around expression if expression type is ExpressionType.Negate
• Add unit test for SQL Server and SQLite providers

---

Concerns

• Are these tests placed in the right place? I couldn't find a set of unit tests for unary expressions.

[dnfadmin]

All CLA requirements met.

[maumar]

use RequiresBrackets helper, so that we don't add parentheses for simple expressions like negate(column) or negate(constant)

[maumar]

also add tests for negate on a column, as well as negate on like expression

[jonlouie]

Thank you for the valuable feedback; I have implemented your suggestions in my latest commits. Please let me know if there's anything I missed or can improve upon.

[smitpatel]

@jonlouie - You will need to sign Contributor License Agreement before we can process this PR.

[jonlouie]

@smitpatel Thank you for the reminder and your patience- had to secure approval before signing the CLA.

[maumar]

@jonlouie I have merged the PR. Thank you for the contribution!

[jonlouie]

@maumar Amazing! Appreciate the fast turnaround and community inclusion :)