fix(lint/useJsxKeyInIterable): handle fragments more comprehensively

[dyc3]

Summary

This PR makes the useJsxKeyInIterable lint handle more cases related to JSX fragments. It can now handle cases like this:

// valid
[].map((item) => {
	return <>{item.condition ? <div key={item.id} /> : <div key={item.id}>foo</div>}</>;
});

// invalid
[].map((item) => {
	return <>{item.condition ? <div /> : <div>foo</div>}</>;
});

related to: #2590

Test Plan

Added snapshot tests

cargo test -p biome_js_analyze use_jsx_key_in_iterable

[codspeed-hq]

CodSpeed Performance Report

Merging #2747 will not alter performance

_{Comparing dyc3:05-06-fix_lint_usejsxkeyiniterable_handle_fragments_more_comprehensively (3abadbe) with main (49cace8)}

Summary

✅ 97 untouched benchmarks

[dyc3]

Once this and #2749 is merged, I have another branch that should completely resolve #2590.

[vohoanglong0107]

In Eslint, using fragments inside an iterator is encouraged by utilizing the Fragment component exported by React:

a.map(e => <Fragment key={e.id}>{e}</Fragment>)

I'm not necessarily advocating for this approach; just providing some food for thought.

[ematipico]

Recursion spotted! 😄 We should remove it

[ematipico]

Mixing a closure approach with internal filtering is not very idiomatic in the Rust world. I suggest using just a loop to collect the information that you require.

[dyc3]

Not sure if I've fixed this the way you want, but it looks a bit cleaner.

[ematipico]

Thank you! We should add a new changelog entry, then we can merge it