[core] Remove custom hooks from the mui-name-matches-component-name linting rule (#42773)

Author: flaviendelangle

.eslintrc.js

@@ -446,16 +446,7 @@ module.exports = {
       files: ['packages/*/src/**/*{.ts,.tsx,.js}'],
       excludedFiles: ['*.d.ts', '*.spec.ts', '*.spec.tsx', 'packages/mui-joy/**/*{.ts,.tsx,.js}'],
       rules: {
-        'material-ui/mui-name-matches-component-name': [
-          'error',
-          {
-            customHooks: [
-              'useDatePickerDefaultizedProps',
-              'useDateTimePickerDefaultizedProps',
-              'useTimePickerDefaultizedProps',
-            ],
-          },
-        ],
+        'material-ui/mui-name-matches-component-name': 'error',
       },
     },
     {

packages/eslint-plugin-material-ui/README.md

@@ -6,6 +6,7 @@ Custom eslint rules for MUI.
 
 - `disallow-active-element-as-key-event-target`
 - `docgen-ignore-before-comment`
+- `mui-name-matches-component-name`
 - `no-hardcoded-labels`
 - `rules-of-use-theme-variants`
 - ~~`restricted-path-imports`~~
@@ -20,6 +21,10 @@ we use already verifies that the passed target can be the target of a
 
 Enforce correct usage of `@ignore` in the prop-types block comments.
 
+### mui-name-matches-component-name
+
+Enforce that the name passed to the `useThemeProps` and `useDefaultProps` hooks matches the component name.
+
 ### no-hardcoded-labels
 
 Prevent the usage of hardcoded labels.