fix(linter/jsx-key): false positive in react/jsx-key

[camc314]

fixes #11916

[camc314]

• fix(linter/jsx-key): false positive in react/jsx-key #11918 👈 (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 #11918 will improve performances by 15.5%

_{Comparing c/06-26-fix_linter_jsx-key_false_positive_in_react_jsx-key (fe4006b) with main (f102cb1)}

Summary

⚡ 1 improvements
✅ 37 untouched benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⚡	mangler[cal.com.tsx]	3.5 ms	3.1 ms	+15.5%

[camc314]

Merge activity

• Jun 26, 9:05 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jun 26, 9:05 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Jun 26, 9:11 AM UTC: Merged by the Graphite merge queue.