Update: fix no-extra-parens CallExpression#callee false negatives

[mdjermanovic]

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

[X] Bug fix

This bug fix produces more warnings.

Tell us about your environment

• ESLint Version: v6.8.0
• Node Version: v12.14.0
• npm Version: v6.13.4

What parser (default, Babel-ESLint, etc.) are you using?

default

Please show your full configuration:

Configuration

module.exports = {
    parserOptions: {
        ecmaVersion: 2015
    },
};

What did you do? Please include the actual source code causing the issue.

Online Demo Link

/* eslint no-extra-parens: "error" */

(a().b)();

What did you expect to happen?

Error and auto-fix to:

/* eslint no-extra-parens: "error" */

a().b();

What actually happened? Please include the actual, raw output from ESLint.

No errors.

What changes did you make? (Give an overview)

Fixed the condition that prevents reporting code such as new (a().b)(), but it didn't account for the fact that the same checkCallNew() function is also used to check CallExpression nodes.

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

These tests were already invalid. Added them because it seems that the existing tests were mostly for NewExpression:

invalid("(a)()", "a()", "Identifier"),
invalid("(a.b)()", "a.b()", "MemberExpression"),
invalid("(a())()", "a()()", "CallExpression"),
invalid("(a.b())()", "a.b()()", "CallExpression"),

These are new errors after this PR:

invalid("(a().b)()", "a().b()", "MemberExpression"),
invalid("(a().b.c)()", "a().b.c()", "MemberExpression"),

[mdjermanovic]

This isn't related to #12740, it's a different bug.

[kaicataldo]

Thanks for contributing to ESLint!