fix(rome_js_analyzer): precedence for useOptionalChain

[ematipico]

Summary

This PR fixes #3257

Test Plan

The PR add two new test cases

[netlify]

✅ Deploy Preview for rometools canceled.

Name	Link
🔨 Latest commit	c423b22
🔍 Latest deploy log	https://app.netlify.com/sites/rometools/deploys/6336e509ecdac90008742223

[github-actions]

Playground for commit a270ee0

[leops]

I'm not sure those are really false positive, it looks more like the fix is simply incorrectly removing the parenthesis: (new foo || {}).bar should be replaced with (new foo)?.bar, but the generated code action emits new foo?.bar instead which then gets re-parsed as new (foo?.bar) and results in a syntax error

[ematipico]

Turns out that the issue was the precedence. If you check the MDN table the new keyword has two different precedence if there are or not arguments.

The absence of arguments yields a unique precedence just for this case, which was not tracked in our enum. I updated the code and it now works as @leops suggested.

[github-actions]

Parser conformance results on ubuntu-latest

js/262

Test result	main count	This PR count	Difference
Total	45879	45879	0
Passed	44939	44939	0
Failed	940	940	0
Panics	0	0	0
Coverage	97.95%	97.95%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	39	39	0
Passed	36	36	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.31%	92.31%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	5946	5946	0
Passed	1621	1621	0
Failed	4325	4325	0
Panics	0	0	0
Coverage	27.26%	27.26%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	588	588	0
Passed	519	519	0
Failed	69	69	0
Panics	0	0	0
Coverage	88.27%	88.27%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	16257	16257	0
Passed	12395	12395	0
Failed	3862	3862	0
Panics	0	0	0
Coverage	76.24%	76.24%	0.00%

[MichaReiser]

Would you mind testing if the formatter handles the precedence correctly and, if not, fix the parentheses setting in its own PR?