fix: sort plugin length for rename

[hyoban]

• <- Keep this line and put an x between the brackts.

Description

  {
    "no-console": "off",
-   "react-dom/no-dangerously-set-innerhtml": "error",
-   "react-naming-convention/component-name": "error",
-   "react-rsc/no-client-hook-in-server-component": "error",
-   "react-web-api/no-leaked-event-listener": "error",
    "react/debug/jsx": "error",
+   "react/dom/no-dangerously-set-innerhtml": "error",
+   "react/naming-convention/component-name": "error",
    "react/no-access-state-in-setstate": "error",
+   "react/rsc/no-client-hook-in-server-component": "error",
+   "react/web-api/no-leaked-event-listener": "error",
  }

Linked Issues

fixes #

Additional context

[antfu]

I am not sure if I understand what is this fixing?

[hyoban]

When renaming plugins that share a common prefix, the rules can mistakenly be applied to the wrong plugin. For instance, @eslint-react/rsc/xxx should become react-rsc/xxx rather than react/rsc/xxx. Currently, this issue may occur because of premature matching, leading to incorrect modifications.