[DataGrid] Fix isRowSelectable when paginationMode='server'

[flaviendelangle]

Fixes #3614

Small performance improvement: we don't call isRowSelectable for every row in GridBody but only on rendered rows.

For the header checkbox, the behavior remain incoherent with paginationMode="server" because we don't know if there are unselected rows on other pages.
I think we can fix that one in a follow up PR by adding a getSelectAllStatus callback for instance, which would return 'all' | 'none' | 'some'.

---

• Tests

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	176.8	389.7	300.9	291.82	78.646
Sort 100k rows	ms	430.3	809.2	781.8	687.92	144.039
Select 100k rows	ms	155.5	266.9	216.9	213.24	36.864
Deselect 100k rows	ms	104.5	515.2	173.7	219.1	151.259

Generated by 🚫 dangerJS against f1e2db7

[m4theushw]

I'm not sure if this change is good. In the previous way, the selection lookup was already filtered all at once and memoized. Now isRowSelectable might be called several times for the same row. I'm OK to call it for every currentPage.rows and memoize the result.

[flaviendelangle]

My thought behind this is that renderedRows will never be hundreds of rows long whereas currentPage.rows might have 100 000 items.
But I could memoize renderedRows and create a memoized selection lookup based on renderedRows.
That way we don't loop on the potentially very long currentPage.rows and we only re-run when the 1st and/or last rendered rows changes.

[github-actions]

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