Currently, the UI only shows 100 runs of a pipeline, even if it has had more than a 100 runs. The backend API for runs of a program defaults to 100 runs. However, it does support pagination, and the UI should support it as well.
Here is the logic:
1. If the number of runs returned in the API are less than 100, use the current logic for displaying runs. There can be no more than 10 pages of size 10 in this case.
2. If the number of runs is 100, there could be more than 10 pages, which should be fetched by specifying the start timestamp as the endTs of the 100th run record, and the end timestamp of current.
Keep repeating 1 and 2 until there are less than 100 runs.
Also, I am not sure about this, but perhaps this can also be used to make pagination more efficient (fetch only 1 page at a time).