fix(eslint-plugin): [no-extra-parens] false positive with arrow generic

[yeonjuan]

Fixes #1587

It occurs because eslint core can't treat well about the checking parens when there is a token(() in type parameter position.

in eslint-utils

        case "CallExpression":
        case "NewExpression":
            if (parent.arguments.length === 1 && parent.arguments[0] === node) {
                return sourceCode.getTokenAfter(
                    parent.callee,
                    isOpeningParenToken
                )
            }
            return null

It seems the eslint-utils treats paren after the callee node as a stop condition for ensuring the paren is not excess paren.
So, #1287 occurs when there is ( in generic and(&&) call expression with one argument.

but it does not make sense because typescript can include ( token in type parameter position.

[typescript-eslint]

Thanks for the PR, @yeonjuan!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

[bradzacher]

This would probably be better as an upstream fix.
The current rule is hacky enough as is, so I'd rather not add too much in the way of extra hacks, when the logic should be able to be fixed at the source.

Example of different rules that I fixed at the source: eslint/eslint#12260
eslint/eslint#11698

[yeonjuan]

@bradzacher Yes :) I agree. I close this PR