feat(ui): set pagination limit to 100 by default

[clementlecorre]

Checklist:

• [c] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

Hello!

Here is a proposal to change the maximum number of workflow on a page.

The pagination is a really cool feature, but I have 1000 workflow to load and it's long (with all).

Thanks !

[alexec]

One of the challenges with this view is that results are returned from the server in a random order, not in time order. Pagination loose this.

[simster7]

As @alexec mentioned, this is unfortunately a limitation from K8s. When we ask K8s to do pagination, it returns all the Workflows in a random order. Because of this, when using pagination we won't be able to show latest Workflows first on the list. Since we believe most users want this ordering, we have set all to be the default.

See kubernetes/kubernetes#80602 (comment) for the K8s issue

[agilgur5]

When we ask K8s to do pagination, it returns all the Workflows in a random order.

Noting here that server-side sorting should be possible after #12736 (running an in-memory SQLite DB)