Bump eslint-plugin-react to ^7.31.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-react	^7.31.10 -> ^7.31.11

---

Release Notes

jsx-eslint/eslint-plugin-react

v7.31.11

Compare Source

Fixed

• [jsx-no-target-blank]: allow ternaries with literals (#​3464 @​akulsr0)
• [no-unknown-property]: add inert attribute (#​3484 @​ljharb)
• [jsx-key]: detect keys in logical expression and conditional expression (#​3490 @​metreniuk)

Changed

• [Perf] component detection: improve performance by avoiding traversing parents unnecessarily (#​3459 @​golopot)
• [Docs] forbid-component-props: inclusive language w/ allowlist (#​3473 @​AndersDJohnson)
• [Docs] automate doc generation with eslint-doc-generator (#​3469 @​bmish)

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[mui-bot]

	Messages
📖	Netlify deploy preview: https://deploy-preview-undefined--material-ui.netlify.app/

No bundle size changes

Generated by 🚫 dangerJS against d4f6154

[Janpot]

All but one of these seem to be false positives. I bet it's caused by jsx-eslint/eslint-plugin-react#3459.

Most of these seem to be detected because we add defaultProps or propTypes properties to functions that aren't react components.

[Janpot]

@michaldudak From jsx-eslint/eslint-plugin-react#3495 (comment)

Why would anything that’s not a React component have propTypes?

I'm also kind of wondering about that 🙂

[michaldudak]

I have no idea what's the use case here. Perhaps @oliviertassinari could shed some light on it?

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.