feat(linter): report vars only used as types

[camc314]

closes #8488

I ported accross the additional tests added in https://github.com/typescript-eslint/typescript-eslint/pull/9330/files, then fixed the resulting test cases

[camc314]

• feat(linter): report vars only used as types #10664 👈 (View in Graphite)
• main

---

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.

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

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #10664 will not alter performance

_{Comparing c/04-28-feat_linter_report_vars_only_used_as_types (387af3a) with main (374e19e)}

Summary

✅ 33 untouched benchmarks
🆕 3 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	linter[RadixUIAdoptionSection.jsx]	N/A	2.7 ms	N/A
🆕	linter[cal.com.tsx]	N/A	1.2 s	N/A
🆕	linter[checker.ts]	N/A	3 s	N/A

[Boshen]

Merge activity

• Apr 28, 9:02 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Apr 28, 9:02 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Apr 28, 9:16 AM EDT: Merged by the Graphite merge queue.