[material-ui][TablePagination] Ability to show, but disable, the first/last page buttons

[cjenkscybercom]

Summary 💡

When paging through results and waiting on the API to return the next set of results, we like to disable the pagination controls. It's possible to do this for the page size dropdown, previous page button, and last page button like so:

<DataGridPro
    slotProps={{
          pagination: {
            showFirstButton: true,
            showLastButton: true,
            backIconButtonProps: {
              disabled: isLoading
            },
            nextIconButtonProps: {
              disabled: isLoading
            },
            SelectProps: {
              disabled: isLoading
            }
          },
        }}
</DataGridPro

However, it doesn't seem to be possible to also disable the first/last buttons.

Examples 🌈

Maybe we could add props for the first/last buttons?

<DataGridPro
    slotProps={{
          pagination: {
            showFirstButton: true,
            showLastButton: true,
            firstIconButtonProps: {
              disabled: isLoading
            },
            backIconButtonProps: {
              disabled: isLoading
            },
            nextIconButtonProps: {
              disabled: isLoading
            },
            lastIconButtonProps: {
              disabled: isLoading
            },
            SelectProps: {
              disabled: isLoading
            }
          },
        }}
</DataGridPro

Or even better...make it possible to entirely disable the pagination controls? (doesn't currently work)

<DataGridPro
    slotProps={{
          pagination: {
            showFirstButton: true,
            showLastButton: true,
            disabled: isLoading
          },
        }}
</DataGridPro

Motivation 🔦

When the user is paging through data, it should be possible to disable the pagination controls while data is loading.

Search keywords: datagrid first last page disable
Order ID: 70139

[MBilalShafi]

Since the grid uses the TablePagination component from the core for this part of the application, I think allowing this enhancement there is better.
I'll transfer the issue there for the team to have a look.

CC @mui/core team