feat(linter): add eslint/block-scoped-var

[huangtiandi1999]

Relates to #479
Rule detail：https://eslint.org/docs/latest/rules/block-scoped-var

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

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

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #10237 will not alter performance

_{Comparing huangtiandi1999:feat/linter/block-scoped-var (5ae9433) with main (2615758)}

Summary

✅ 9 untouched benchmarks
🆕 27 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	codegen[checker.ts]	N/A	22.1 ms	N/A
🆕	codegen_sourcemap[checker.ts]	N/A	65.1 ms	N/A
🆕	formatter[antd.js]	N/A	709.6 ms	N/A
🆕	formatter[react.development.js]	N/A	8 ms	N/A
🆕	formatter[typescript.js]	N/A	1.1 s	N/A
🆕	mangler[antd.js]	N/A	15.9 ms	N/A
🆕	mangler[react.development.js]	N/A	294.2 µs	N/A
🆕	mangler[typescript.js]	N/A	39.5 ms	N/A
🆕	minifier[antd.js]	N/A	163.6 ms	N/A
🆕	minifier[react.development.js]	N/A	1.8 ms	N/A
🆕	minifier[typescript.js]	N/A	287.9 ms	N/A
🆕	estree[checker.ts]	N/A	96.8 ms	N/A
🆕	parser[RadixUIAdoptionSection.jsx]	N/A	89.2 µs	N/A
🆕	parser[antd.js]	N/A	105.5 ms	N/A
🆕	parser[cal.com.tsx]	N/A	29.1 ms	N/A
🆕	parser[checker.ts]	N/A	53.2 ms	N/A
🆕	parser[pdf.mjs]	N/A	16.8 ms	N/A
🆕	semantic[RadixUIAdoptionSection.jsx]	N/A	73.1 µs	N/A
🆕	semantic[antd.js]	N/A	103.4 ms	N/A
🆕	semantic[cal.com.tsx]	N/A	25.9 ms	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[camc314]

thanks!

[camc314]

i think the perf drop, while not ideal is ok. checker.ts has a lot of var declarations that this rule needs to check, and i can't see any obvious ways to improve the perf of this rule