fix(js_parser): correctly parse type arguments in expression

[ah-yu]

Summary

Try to close #1184

When parsing type arguments in an expression, it is necessary to re-scan the closing > token to ensure that it is > rather than other tokens, such as >=

Typescript reference https://github.com/microsoft/TypeScript/blob/2e3b8af85e1f782634349139819151881369e3ea/src/compiler/parser.ts#L6529-L6532

Test Plan

Add a new test case

[netlify]

✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	b691ce8
🔍 Latest deploy log	https://app.netlify.com/sites/biomejs/deploys/65b07bd9603db10008a59bfb
😎 Deploy Preview	https://deploy-preview-1645--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (🟢 up 1 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 93 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codspeed-hq]

CodSpeed Performance Report

Merging #1645 will not alter performance

_{Comparing ah-yu:parser_0 (b691ce8) with main (c3fee4e)}

Summary

✅ 93 untouched benchmarks

[ah-yu]

@Conaclos Thank you for the review! I have addressed the comments in 8b2b4e9

[Conaclos]

Great fix :)