read all repos in org with pagination

[Barbapapazes]

🔗 Linked issue

fix #74

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This support pagination by permitting to pass page and per_page parameters. In the same time, it will also store and return the Link header provided by the API.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

I think we can handle the pagination once and return theall pages instead of asking API consumers to do it.

[BobbieGoede]

This would be a nice addition (and would resolve allow us to resolve issues like nuxt/scripts#295).

@Barbapapazes / @pi0
I can look into implementing the suggested changes if necessary, I assume you meant returning the complete merged/concatenated results? I suppose that boils down to making requests until the result count is less than per_page (may make the response big depending on the request/repo).