[DataGridPro] Make @mui/x-data-grid-pro import shared code from @mui/x-data-grid

[flaviendelangle]

Part of #924
Fix #2245

Codesandbox playground for DataGridPro

Note: The proptypes generation is broken for pro-only components. Will be fixed in #3953.

In this PR

• Move almost all the pro-only code into packages/grid/x-data-grid-pro/src

• Import the shared code from @mui/x-data-grid instead of packages/grid/_modules_

This code should not be released as is, we should drop the whole _modules_ folder before to avoid problems.

What's next ?

• Move all the community code into packages/grid/x-data-grid/src and drop packages/grid/_modules_/

• Migrate @mui/x-data-grid, @mui/x-data-grid-pro and @mui/x-data-grid-generator to the core bundling strategy (see [core] Migrate @mui/x-license-pro to the new bundling strategy #3738)

• In @mui/x-data-grid-pro, replace the imports from the the root of @mui/x-data-grid prefixed with unstable with imports from @mui/x-data-grid/internals/xxx

• Stop listing the pro-only events in GridEvents (we will probably need to replace the enum with type GridEvents = keyof GridEventLookup, which is a breaking change) - Need v6

• Stop listing the pro-only components in GridSlotsComponent

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	210.8	369.7	246.9	275.2	58.612
Sort 100k rows	ms	381.5	887.5	614.3	620.06	161.242
Select 100k rows	ms	182.7	303.2	257.4	245.62	40.66
Deselect 100k rows	ms	137.6	283.5	204.8	197.28	53.083

Generated by 🚫 dangerJS against b6fc731

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[m4theushw]

I'll do a more detailed review once #3953 is ready. With the _modules_ folder it's complicated to see the impact of this PR.

[m4theushw]

It needs to be exported to avoid a breaking change.

[flaviendelangle]

Good catch, I'll do a double check on the export files

[m4theushw]

I thought we would have a Pro GridColDef, instead of using module augmentation.

As example:

Suggested change

	import { GridColDef } from '@mui/x-data-grid';
	import { GridColDef } from '../../../gridColDef';

But we can see how this approach works in the long term.

[flaviendelangle]

I think we should have a pro GridColDef at one point
But it was creating too many problems with the api params deep inside some GridColDef callbacks.
So I went for the easy way for now.

[flaviendelangle]

@m4theushw for you deep review, I propose to do it on the new bundling strategy PR (after #3953)
At that point, @mui/x-data-grid-pro should not export the DataGrid component for instance.
So comparing export snapshots between the last release and this PR should give you a clearer vision of what has been added or removed.