refactor(semantic)!: remove ModuleRecord from Semantic

[Boshen]

ModuleRecord will eventually be moved to be linter specific thing for cross module data sharing, which means we can add more data to it.

[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.

[Boshen]

• refactor(semantic)!: remove ModuleRecord from Semantic #7548 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Merge activity

• Nov 29, 11:36 AM EST: A user merged this pull request with the Graphite merge queue.

[codspeed-hq]

CodSpeed Performance Report

Merging #7548 will degrade performances by 4.63%

_{Comparing 11-30-refactor_semantic_remove_modulerecord_from_semantic_ (0be5233) with main (8a788b8)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 28 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	main	11-30-refactor_semantic_remove_modulerecord_from_semantic_	Change
❌	linter[cal.com.tsx]	1.1 s	1.1 s	-4.63%
⚡	semantic[RadixUIAdoptionSection.jsx]	80.5 µs	74.9 µs	+7.5%