fix(linter/unicorn): add support for Array.from() for prefer-set-size rule

[baevm]

fixed commented out tests in #19428 for Array.from() in unicorn/prefer-set-size rule

[Copilot]

Pull request overview

Adds Array.from(set).length detection and auto-fixing to the unicorn/prefer-set-size rule, aligning behavior with existing [...set].length support and re-enabling previously commented-out test cases.

Changes:

• Extend the rule matcher to recognize Array.from(<set>).length as a convertible Set-to-array pattern.
• Update the fixer to replace the whole conversion expression with the underlying Set expression and change .length → .size where safe.
• Expand rule tests and refresh the snapshot output to cover the new cases (including “no-fix” scenarios when comments would be dropped).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
crates/oxc_linter/src/rules/unicorn/prefer_set_size.rs	Implements Array.from(...) pattern detection, adjusts fix strategy, and adds/updates test & fix expectations.
crates/oxc_linter/src/snapshots/unicorn_prefer_set_size.snap	Updates snapshot diagnostics/help text and includes new Array.from(...) failure cases.

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 47 skipped benchmarks¹

---

_{Comparing baevm:prefer-set-size-fix-array-from (c73e601) with main (139ddd9)²}

Footnotes

1. 47 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (742fc9f) during the generation of this report, so 139ddd9 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[camc314]

Thank you!