feat: enhance dom/no-string-style-prop rule to support custom components and improve attribute resolution

[Rel1cx]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• Test
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
eslint-react	Ready	Preview	Comment	Sep 5, 2025 4:04pm

[Copilot]

Pull Request Overview

This PR enhances the dom/no-string-style-prop ESLint rule to support custom components and improve attribute resolution. The rule now uses a more sophisticated JSX element resolver instead of a simple JSX attribute visitor, enabling better handling of custom components with style attributes.

Key changes:

• Replace simple JSXAttribute visitor with JSXElement visitor using new resolver utilities
• Add support for custom components through createJsxElementResolver and resolveAttribute functions
• Remove custom getAttributeValueText function in favor of the shared utility

Reviewed Changes

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

File	Description
no-string-style-prop.ts	Refactored rule implementation to use new resolver utilities for better attribute resolution
no-string-style-prop.spec.ts	Added test case for custom component with style attribute that should be allowed

---

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

[Rel1cx]

Support #1217 by utilizing the existing additionalComponents configuration.