feat(coverage): enable regexp in test262

[Boshen]

@leaysgur This enables all test262 regexp tests, feel free to decide when's the right time to integrate.

It seems like we need to add some pointing spans on the diagnostics.

It's somewhat slow to run just c, so I always use just example parser for local development.

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[codspeed-hq]

CodSpeed Performance Report

Merging #4242 will degrade performances by 12.6%

_{Comparing regexp-tests (8a2f7a1) with regexpp (b16c6f4)}

Summary

❌ 4 regressions
✅ 25 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	regexpp	regexp-tests	Change
❌	minifier[antd.js]	214.8 ms	227.8 ms	-5.7%
❌	parser[antd.js]	104.2 ms	119.3 ms	-12.6%
❌	parser[pdf.mjs]	17.1 ms	18.2 ms	-5.97%
❌	transformer[antd.js]	245.3 ms	260.4 ms	-5.81%

[IWANABETHATGUY]

Reparsing each regex eagerly in place sounds not reasonable, can we introduce another visit pass (enabled by a option) and reparse each regex then emit diagnostic at the end?

[IWANABETHATGUY]

Most downstream users of parser may not care about whether the regex semantic is correct or not like formater, bundler.

[leaysgur]

But actually, I'm also concerned about how to finish this PR.

With current code, oxc_parser parses RegExp and reports errors, but does not seem to hold the parsed results.

@Boshen What were your original plans?

[leaysgur]

FYI:

• The previous CodSpeed result was one where the entire source code(!) was passed to the regexp parser, not the regular expression part
• I have not yet been started parser perf improvements

[IWANABETHATGUY]

FYI:

• The previous CodSpeed result was one where the entire source code(!) was passed to the regexp parser, not the regular expression part
• I have not yet been started parser perf improvements

Thanks for your explanation