fix(linter): allow underscore-prefixed useState bindings

[Baltsat]

Summary

• treat an underscore-prefixed useState getter or setter as intentionally unused
• skip the pair-name convention when either binding is intentionally unused
• cover both exact _ placeholders and descriptive _unused... names on both tuple positions

Fixes #24952.

Proof

• exact unpatched base reproduced all four false positives
• focused react/hook-use-state rule test passed
• cargo test -p oxc_linter: 1,175 passed, 0 failed, 1 ignored, plus integration tests and doctests
• linter crate lint passed
• formatting check passed
• linter code generation completed without changing generated files
• production-only revert made the four new cases fail; restoring the final tree returned the focused test to green
• git diff --check passed

AI assistance: I used Codex during implementation and test iteration. I reviewed the final one-file diff, the rule behavior, and the complete proof above before submission.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[baevm]

See also: #24952 (comment)

[Baltsat]

Yes — both upstream rules currently report these forms. This patch intentionally implements the narrower behavior requested in #24952: only an explicitly _-prefixed tuple binding is treated as an intentional placeholder; omitted or otherwise mismatched pairs remain errors.

So the project-level choice is whether Oxlint wants strict upstream parity here. If it does, #24952 is already expected behavior and this change should not land. If Oxlint wants to recognize the conventional explicit-unused marker, this patch keeps that divergence limited to the two requested positions and locks it with focused cases.