[GraphQL] Show up to 200 jobs per CI stage
What does this MR do?
In the pipeline graph, if the GraphQL backend doesn't return all of the jobs (due to pagination) the frontend breaks because it expects all of the jobs to be there in order to render the pipeline graph properly. This MR increases the max page size to cover 99% of use cases without removing the limit altogether.
Related #336319 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Edited by Matija Čupić