fix(linter): fix false positives in exhaustive-deps

[camc314]

part of #7246

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

[camc314]

• fix(linter): false positive in exhaustive-deps #7626
• fix(linter): update reporting spans for exhaustive-deps #7625
• fix(linter): fix false positives in exhaustive-deps #7615 👈 (View in Graphite)
• main

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

[codspeed-hq]

CodSpeed Performance Report

Merging #7615 will degrade performances by 3.21%

_{Comparing c/12-03-fix_linter_fix_false_positives_in_exhaustive-deps (543df6e) with main (9b803d9)}

Summary

❌ 1 regressions
✅ 28 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	main	c/12-03-fix_linter_fix_false_positives_in_exhaustive-deps	Change
❌	semantic[cal.com.tsx]	28.2 ms	29.1 ms	-3.21%

[Boshen]

Merge activity

• Dec 3, 6:53 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 3, 6:53 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 3, 7:01 PM EST: A user merged this pull request with the Graphite merge queue.