nvchecker approach will hammer our GitLab server

The nvchecker script checks packages by fetching a .SRCINFO and .nvchecker.toml this likely is going to cause some extra load on our GitLab server which already struggles with Git.

Possible options:

• Introduce a Git mono-repo for all packages using a subtree, still going to be intense for GitLab and might not scale?
• Use the GitLab API

We have two files we are interested in fetching so in theory we can easily cache them and only fetch it when required. The question is how we easily obtain the "last modified" state for these files. A simple solution would be whenever anything in Git changes.

So an option is to do a query for last commit since $checkdate and if there was any fetch files.

Or use the projects API and use updated_at although this is a fairly vague field and might also trigger when an issue is created. Or alternatively use {statistics: commit_count: X}. Any change in commits would require to re-fetch the files.

Likely we want to use graphql (Brrrr) as then we can do multiple requests at once.