Fix: new-parens false negative (fixes #6997)

[mysticatea]

Fixes #6997.

This PR changes the logic of new-parens.
Old logic counts parentheses in a NewExpression node. Then OK if it's 2 or more.
New logic checks a token (except )) preceded by the callee of a NewExpression. Then OK if the token is an opening parenthesis and is inside of the NewExpression node.

NOTE: this needs minor bump.

[mention-bot]

@mysticatea, thanks for your PR! By analyzing the annotation information on this pull request, we identified @vitorbal, @pmcelhaney and @ilyavolodin to be potential reviewers

[eslintbot]

LGTM

[nzakas]

Minor bumps should have "Update:" instead of "Fix:" for the commit message.

[nzakas]

Code LGTM. Can you also update the docs to show this?

[eslintbot]

LGTM

[eslintbot]

LGTM

[mysticatea]

Oops, I'm sorry, I had misunderstood that Update: is for enhancements.

[nzakas]

Yeah, we changed it to also be when a rule produces more warnings. From http://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changesa-namestep2a:

Update - for a backwards-compatible enhancement or a change to a rule that increases the number of reported problems.

[platinumazure]

@nzakas Does that also imply that we should label issues with enhancement as well? I think the docs mention somewhere else that you can/should use the issue label to determine your commit summary prefix.