[DataGrid] Add codemods for v6 breaking changes

[MBilalShafi]

Codemods for pickers can be found here

The v6 for DataGrid is bringing quite a few breaking changes.
To ease users' migration we ought to try and cover as most changes with codemods as possible.

The codemod package can be found here. It contains all the core setup needed in order to add new codemods to it.

This is intended as an umbrella issue to group all the codemods needed for v.6.x migration for DataGrid.
Ideally as much migrations as possible should be provided with preset-safe codemod.

The process of adding a new codemod

• One of the existing codemods can be used as an example (i.e.: localization-provider-rename-locale)
• copy or create a new folder for your codemod
• all the relevant code that is eventually shipped to the user is in index.ts
• update/provide tests for your newly created codemod (test fixtures are authored as js files to allow as minimal syntax as you want—without triggering ts issues)
• if your codemod is safe to add to preset-safe—update this codemod with your newly added codemod making sure the codemods order is correct if codemod is sensitive to that (i.e. separate props should firstly be migrated to componentProps and only later be passed through a codemod renaming componentProps to slotProps if we'd go with such approach)
• update README file with your newly added codemod
  You can check @mui/codemod for inspiration on more advanced migration cases.

How to test your changes locally (on a different project)

P.S. yarn link does not create a bin command from a linked package

• run build with either yarn workspace @mui/x-codemod build or yarn build if you are in src/packages/x-codemod
• run cd build && yarn pack
• copy the built 7.tgz file to the root of your project you want to run (test) the codemod in
• add "@mui/x-codemod": "file:./<your_package_name>" into your project dependencies
• run yarn install
• now you can run the codemod in the way you prefer (either through npx @mui/x-codemod v6.0.0/preset-safe src or by adding an x-codemod script in your project)
• caveat: testing iterative changes might result in a cached package version being used instead of your latest modification. You can either use a unique package name (possibly quicker) each time or clean npm cache each time.

Breaking changes requiring codemods

Breaking changes related to DataGrid are documented here and relevant PRs are available with applied filters.

• rename-row-selection-props doc | change PR
• remove-deprecated-props doc | change PR
• rename-state-access-selectors doc | change PR
• rename-events doc | change PRs: 1, 2
• rename-api-ref-methods doc | change PR
• remove-deprecated-api-methods doc | change PR - requires manual work on developer's part, better not handle using codemods
• refactor-filter-item-props doc | change PR
• remove-removed-exports-and-types doc | change PR - requires manual work on developer's part, better not handle using codemods
• replace-null-undefined-render-cell doc | change PR Could be a lot of different possible cases all of which may not be covered by codemod
• replace-column-menu-components doc | change PR
• remove-disableExtendRowFullWidth-prop change PR
• rename-link-operator-logic-operator doc | change PR
• remove-column-types-props doc | change PR Needs user intervention, better not be done via codemod
• rename-rowsPerPageOptions-to-pageSizeOptions change PR
• error-overlay-import-rename change PR ErrorOverlay component removed in [DataGrid] Remove error boundary #7579, the new change will require some manual work
• components-componentsProps-to-slots-slotsProps change PR