[core] Stop using an enum for GridPreProcessingGroup

[flaviendelangle]

Extracted from #3688

100% core, no impact for users.

Enums can't be extended between the community and the pro package.
For the pre-processing I reverted the logic by generating the type as the keys of the lookup.
Maybe the GridEvents could also be a type instead of an enum in v6.

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	1,498.9	2,716.1	1,717.4	2,040.46	506.317
Sort 100k rows	ms	966.6	1,594	1,562.3	1,377.76	237.745
Select 100k rows	ms	241.3	306.4	284.3	278.38	21.777
Deselect 100k rows	ms	156.6	380.1	195.1	229.28	78.874

Generated by 🚫 dangerJS against 4425b38

[alexfauquette]

I'm not that much familiar with typescript. That's what I understand:

The GridPreProcessingGroup enum can not be extended which is a problem to add for example row grouping.

So instead, you use keyof GridPreProcessingGroupLookup which is equivalent to
'hydrateColumns' | 'scrollToIndexes' | ...

This type is used for the unstable_applyPreProcessors to indicate to which group the preprocessor must be applied

If yes, its good for me

[flaviendelangle]

@alexfauquette Exactly, and it is also used to type directly the callbacks

  const updateSelectionColumn = React.useCallback<
    GridPreProcessor<GridPreProcessingGroup.hydrateColumns>
  >()

Becomes

  const updateSelectionColumn = React.useCallback<GridPreProcessor<"hydrateColumns">>()