Update: Fix handling of chained new expressions in new-parens

[mdjermanovic]

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

[X] Bug fix

This bug fix can produce more errors by the new-parens rule in some cases. Also fixes wrong autofix in some other cases.

Tell us about your environment

• ESLint Version: 6.4.0
• Node Version: 10.16.0
• npm Version: 6.9.0

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.

Demo link 1

/* eslint new-parens:["error", "always"] */

new new foo();

Demo link 2

/* eslint new-parens:["error", "never"] */

new new foo();

What did you expect to happen?

1 error and the following autofix for the first example:

/* eslint new-parens:["error", "always"] */

new new foo()();

1 error and the following autofix for the second example:

/* eslint new-parens:["error", "never"] */

new (new foo);

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

0 errors in the first example:

/* eslint new-parens:["error", "always"] */

// false negative, the outer `new` does not have parens.
new new foo();

2 errors and a bit invalid autofix in the second example:

/* eslint new-parens:["error", "never"] */

// false positive for the outer `new` and invalid autofix - wrong place for parens
(new new foo);

What changes did you make? (Give an overview)

Check that the parens are not a part of the child node.

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

[mysticatea]

LGTM, thank you!