[material-ui][base-ui][TablePagination] Accept readonly array for rowsPerPageOptions prop

[pcorpet]

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Netlify deploy preview

https://deploy-preview-40481--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 69cc5eb

[oliviertassinari]

The direction looks good, same as #25155. I don't know if we need a test case for this.

It even looks like we should do this change everywhere in the codebase while we are at it. For example:

• material-ui/packages/mui-base/src/Unstable_Popup/Popup.types.ts

  Line 60 in 48a2922

  middleware?: Array<PopupMiddleware | null | undefined | false>;

• material-ui/packages/mui-base/src/useSlider/useSlider.ts

  Line 145 in 48a2922

  newValue: number | Array<number>,

• material-ui/packages/mui-base/src/useSlider/useSlider.types.ts

  Line 102 in 48a2922

  value?: number | number[];

[pcorpet]

I'm just a humble user of MUI and didn't want to move too many things at once. Do you want me to do that in that PR as well?

[oliviertassinari]

@pcorpet I'm not responsible for reviewing PRs anymore. I landed here from @zannager. My comment was more to raise to maintainers the value of carrying the idea behind this PR in the whole codebase (#25155 was already a sign). There don't seem to be downsides, only DX upsides:

[oliviertassinari]

rowsPerPageOptions is defined 3 times, for 3 different components, I think we should update all.

[ZeeshanTamboli]

The changes look good. I've updated the prop in Material UI Table Pagination. I believe no tests are necessary for this. We can address the other mentioned props here in separate PRs. Thanks, @pcorpet!