[internal] Remove custom hooks from the mui-name-matches-component-name linting rule

[flaviendelangle]

The config now lives on the X repo.
And these custom hooks are blocking the PigmentCSS migration on the pickers.

[mui-bot]

Netlify deploy preview

https://deploy-preview-42773--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 708dce0

[Janpot]

Looks good to me.

Had to dig a bit more than needed to figure out what this does. If you're up for it, I'd suggest to update the README with a short description of what this rule is supposed to cover.

[flaviendelangle]

I can add it to the README, but checking its implementation changed in #42638

@siriwatknp does it mean that the rule will stop working with useThemeProps?
We are still using useThemeProps in MUI X and we can't migrate to useDefaultProps before the next major.
Also I just migrated all the pickers to use createUseThemeProps and I see that you removed its usages in the pull request above 😬 , if you could communicate any change in DX around the Pigment CSS migration to avoid back and forth work on our side that would be great.

[siriwatknp]

@siriwatknp does it mean that the rule will stop working with useThemeProps? We are still using useThemeProps in MUI X and we can't migrate to useDefaultProps before the next major. Also I just migrated all the pickers to use createUseThemeProps and I see that you removed its usages in the pull request above 😬 , if you could communicate any change in DX around the Pigment CSS migration to avoid back and forth work on our side that would be great.

Nope, I reverted in #42817. It should work the same for MUI X.

[flaviendelangle]

👌 awesome
I'll add some doc about this lint rule in the README before merging this PR then