Fix: no-mixed-operators false positives with ? : (fixes #14223)

[mdjermanovic]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

fixes #14223

Fixes false positives such as:

/* eslint no-mixed-operators: ["error", { groups: [["&&", "||", "?:"]] }] */

a ? (b || c) : d; // false positive

(a) ? (b || c) : d; // ok

(a ? (b || c) : d); // also ok

//--------------------------------

a ? b : (c || d); // false positive

(a) ? b : (c || d); // ok

(a ? b : (c || d)); // also ok

What changes did you make? (Give an overview)

Removed invalid isMixedWithConditionalParent() check.

The other check, isMixedWithParent(), already covers binary/logical expression nodes in conditional expressions, so !astUtils.isParenthesised(sourceCode, node.test) condition in isMixedWithConditionalParent() was redundant for child binary/logical expressions in test, and wrong for child binary/logical expressions in consequent/alternate.

!astUtils.isParenthesised(sourceCode, node) condition in isMixedWithConditionalParent() was also wrong. It gets a ConditionalExpression node when its child binary/logical expression node is being checked, so checking parens around the ConditionalExpression in that case doesn't make sense.

Is there anything you'd like reviewers to focus on?

[nzakas]

LGTM