Related #57669

What problem does this address?

Third parties can start extending some of our DataViews-based screens, such as the Pages page, via registerEntityAction and unregisterEntityAction.

While desired, this can grow wildly if unchecked: for example, I presume most plugins will want its actions to be primary. I've done a quick test by setting all existing actions as primary to see how the screen scales and this is what I've got:

What is your proposed solution?

We should look at how to alleviate this UI tension derived from extensibility.