fix: add pagination to job_collector task

[ClaudioMascaro]

⚠️ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

• I have read through the Contributing Documentation.
• I have added relevant tests.
• I have added relevant documentation.
• I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary

Add pagination in github_graphql job collector task.

Does this close any open issues?

Closes #8028

Screenshots

We needed to extract data from a large and complex repository, which has over 30000 workflow runs, and some of that can have more than 200 job runs.

Whenever the Collect Job task started, It simply wouldn't finish the query in time, entering in the retry flow:

we have tried to reduce api timeout, but it would only increase the number of unsuccessful retries:

So, after implementing the solution, it would solve our case, and after 17 hours, it was able to collect all data:

(don't mind the log I added locally to debug)

as for comparison purposes, we have extracted data from a much less complex repository, which before the implementation, took the following time:

and, after bringing off the solution (of course, rerunning in hard refresh mode), there was no change in pipeline overall time:

Other Information

Already merged on main branch, reopening as requested: #8233 (review)

[ClaudioMascaro]

@klesh

[klesh]

This looks good! Could you also update the end-to-end (e2e) test cases to reflect these changes? Thanks!

[ClaudioMascaro]

@klesh do you have any example on writing e2e test for Collector tasks? I couldn't find any practical approach to that. Also there are tests failing for jira plugin.

[klesh]

Yes, that's unexpected; collectors shouldn't impact e2e tests.

Further investigation revealed that PR #8223 introduced the error, which I've addressed in PR #8243. Everything should be working correctly now.

My apologies for the inconvenience, and thank you for your contribution!