fix: new (foo?.bar)() incorrectly throws exception OptionalChainingNoNew

[liuxingbaoyu]

Q	A
Fixed Issues?	Fixes #15376
Patch: Bug Fix?	√
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	√
Documentation PR Link
Any Dependency Changes?
License	MIT

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/53807/

[liuxingbaoyu]

I'm surprised that the test262 parser tests don't cover this. :)

[JLHwung]

Can you add a new test case for non null TS expression?

// invalid
new foo?.bar!()

[liuxingbaoyu]

Yes, this test should throw an exception, but it doesn't.
But unfortunately I didn't find a good way to fix it.
The ast of ts is different from ours. It splits this statement into call(non-null(prop-access(new,question,id))).

[JLHwung]

Maybe we can move the error reporting here?

babel/packages/babel-parser/src/parser/expression.ts

Line 771 in 41aac8b

if (noCalls && this.lookaheadCharCode() === charCodes.leftParenthesis) {

When noCalls is true, we should throw the error anyway. If the next token is ( we stop otherwise we continue for the error recovery mode. As a bonus, we don't have to deal with extra?.parenthesized (because it will be descended from parseExprAtom instead) and it should work with non null TS expression, too.