feat(parser,linter)!: use a different ModuleRecord for linter

[Boshen]

The parser returns a simple ModuleRecord that is allocated in the arena for performance reasons.

The linter uses a more complicated, Send + Sync ModuleRecord that will hold more cross-module information.

The next step is to return more esm information from the parser to eliminated the need of the oxc_module_lexer crate.

[graphite-app]

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

Add the label “0-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 #7554 will improve performances by 33.04%

_{Comparing 11-30-feat_parser_linter_separate_modulerecord_ (c2ced15) with main (7e42e71)}

Summary

⚡ 3 improvements
✅ 27 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	11-30-feat_parser_linter_separate_modulerecord_	Change
⚡	isolated-declarations[vue-id.ts]	945.8 ms	710.9 ms	+33.04%
⚡	parser[RadixUIAdoptionSection.jsx]	98.4 µs	87 µs	+13.08%
⚡	parser[cal.com.tsx]	32.7 ms	29.1 ms	+12.26%

[Boshen]

Merge activity

• Nov 30, 10:56 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 30, 11:02 AM EST: A user added this pull request to the Graphite merge queue.
• Nov 30, 11:06 AM EST: A user merged this pull request with the Graphite merge queue.