feat(linter): add react/forbid-dom-props rule

[baevm]

This PR adds react/forbid-dom-props rule, issue #1022

[graphite-app]

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.

[Copilot]

Pull Request Overview

This PR implements the react/forbid-dom-props rule for the linter, which allows preventing the use of specific props on DOM elements in React JSX. The rule is configurable to forbid certain props either globally or only on specific DOM elements, with optional custom error messages.

Key changes:

• Added the new forbid_dom_props rule implementation with comprehensive configuration support
• Added comprehensive test cases covering various configuration scenarios
• Integrated the rule into the linter's module system

Reviewed Changes

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

File	Description
crates/oxc_linter/src/rules/react/forbid_dom_props.rs	Main implementation of the forbid_dom_props rule with configuration parsing and linting logic
crates/oxc_linter/src/rules.rs	Added module declaration and rule registration for forbid_dom_props
crates/oxc_linter/src/snapshots/react_forbid_dom_props.snap	Test snapshot file containing expected error outputs

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codspeed-hq]

CodSpeed Performance Report

Merging #14365 will not alter performance

_{Comparing baevm:react/forbid-dom-props (d8d2090) with main (831974f)}

Summary

✅ 4 untouched
⏩ 33 skipped¹

Footnotes

1. 33 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. ↩

[camc314]

Thank you!