Unify and fix accessibility of the various Pagination components

[afercia]

Description

The editor uses a few user interfaces where pagination buttons are in place. For example:

• dataviews
• patterns explorer
• global styles revisions
• possibly other places I may have missed

While theoretically these pagination are very similar and should work in a very similar way, they are all different and use different components.

From an accessibility perspective, there are a few issues. Most notably:

• Buttons get dynamically disabled while they are focused, thus triggering a focus loss. See Make sure disabled buttons are always focusable by default #56547
• The buttons don't show a tooltip so that their accessible name isn't visually exposed.

I'd tend to think these pagination tools should work and look the same way throughout the whole user interface.
It's also a good opportunity to fix the most relevant accessibility issuses and abstract some code.

Screenshots:

Dataviews pagination:

Patterns explorer pagination:

Global styles revisions pagination:

NEW: Pages pagination: note: as far as I can tell this is the only case where the buttons do not trigger a focus loss because they use arira-disabled instead of disabled. Tooltips work as well. The implementation of the current page indicator is arguable though as it's a mix of translatable strings and labeling / value of the <select> element.

Step-by-step reproduction instructions

• Test one of these paginations for example the global styles one.
• Go to Site editor > Styles > Revisions.
• Use the keyboard and Tab to the 'Last page' button.
• Observe the button doesn't show a tooltip.
• Press Enter.
• Observe the 'Last page' button is now not focusable because it has a disabled HTML attribute.
• Observe focus is lost: press Tab again and observe the tab order starts from scratch from the document root.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[mikachan]

Noting that the Font Library modal also includes a pagination implementation, also discussed in #59591.

[t-hamano]

Related to this issue, I suggested adding the Pagination component.

#55650