refactor(coral): Replace custom Pagination with Aquarium Pagination

[mathieu-anderson]

What is currently missing?

We have a custom Pagination component (src/app/components/Pagination). The reasons for it to exist are twofold:

• sub-optimal: shortcomings in a11y for Aquarium's Pagination (screen reader desctipions are not enough to know that the component is a Pagination UI)
• breaking: a bug that prevented us from setting an initial page from the URL search params (https://github.com/aiven/design-system/issues/946)

Using custom components when one already exists in Aquarium is not desirable at this point.

How could this be improved?

The breaking issue has been resolved, and will be released in an upcoming Aquarium version. We should consider using the component as soon as the bug is fixed in the released version, and opening an issue with the Aquarium project to fix the a11y ambiguity.

Todo:

• replace use of custom Pagination by Aquarium's Pagination
• delet custom Pagination
• open a11y issue in the Aquarium project

Is this a feature you would work on yourself?

• [ ] I plan to open a pull request for this feature

[programmiri]

Note about a11y

• screen reader does not have any information that this is a navigation and how to use it
• focus states for keyboard may not work (our accessibility.css may already cover that)
• hover state of buttons is not even enough for AA compliance, which it at least should be

This should be fixed before using the component (either temp fix on our end or in DS) and we can use the temp implementation we already have until it works. Otherwise we willingly break functionality for certain users for an unclear amount of time without any need and value other than removing a bit of code. (removing code is super nice, but not if users pay the price ^^)