[data grid] Check focus validity whenever the rows in state changes

[flaviendelangle]

Fixes #4678

Before this PR, we where listening to props.rows changes to check the focus validity.
Now I listen to GridEvents.rowsChange to also track changes with apiRef.current.updateRows or grouping changes.

I don't think we need to listen to sortedRowChange and pagination change. If the focus is on a non-visible row, it does not causes any crash.

---

I also removed unused unused props.rows from useGridDimensions typing
That way only useGridRows accesses directly props.rows, all other hooks should use the state.

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	274.2	617.3	333.7	418.8	140.353
Sort 100k rows	ms	538.5	1,000.1	562.1	760.58	182.938
Select 100k rows	ms	119.1	203.3	202	185.44	33.189
Deselect 100k rows	ms	103.6	212.5	182.9	168.36	39.044

Generated by 🚫 dangerJS against 9070a1f

[github-actions]

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

[m4theushw]

In theory, every time a cell loses focus it should publish cellFocusOut, but to publish it we call getCellParams which will crash because the row doesn't exist. It will be a bug if the removed row was also being edited. If we want to implement the option 3 from #4516 (comment) we will likely have to revisit this part. Maybe we change the params passed to cellFocusOut to not include the row object. Anyway, until someone complains about cellFocusOut not published we can keep the listener to rowsSet.

[flaviendelangle]

Yes, in v6 we could pass the id instead of the params to allow to publish the focus out event on a destroyed cell.