[core] Auto-fix upcoming eslint issues

[Janpot]

Running yarn lint --fix on #34642 without upgrading eslint

To reviewers: recommended to hide whitespace to drastically reduce the line count

edit:

this messes with the tooltip in the demos:

[mui-bot]

Details of bundle changes

Generated by 🚫 dangerJS against c49770d

[Janpot]

@michaldudak Since this is a large PR, I'm specifically calling attention to the removal of fragment in the base demo: https://github.com/mui/material-ui/pull/34644/files#diff-036fe9f47ed568c74dc41779902387e3faf8b49a20818792e906da08a91f84e3L9. Just in case it's there for a reason

[michaldudak]

@Janpot it seems that the demo works correctly after your change.

I'm wondering, what's the rationale for disallowing components as lambdas?

[Janpot]

@michaldudak airbnb/javascript#2505 (comment)

I also remember it at some point to be a requirement for react-refresh to work correctly in Next.js, though I can't immediately find it back.

[michaldudak]

Looks good to me now!

[oliviertassinari]

Great :)

[Janpot]

@michaldudak Just stumbled upon it while looking for something else: https://nextjs.org/docs/basic-features/fast-refresh#limitations

Anonymous arrow functions like export default () => <div />; cause Fast Refresh to not preserve local component state. For large codebases you can use our name-default-component codemod.

[michaldudak]

Always good to learn something new, thanks!

[oliviertassinari]

@m4theushw A heads up, the eslint configuration is going to change. If we could apply the same auto-fix cases in MUI X, it would be great.