More grouping of renovate PR's

[fpgmaas]

PR Checklist

• A description of the changes is added to the description of this PR.
• If there is a related issue, make sure it is linked to this PR.
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added or modified a feature, documentation in docs is updated

Description of changes

Currently, we get quite a lot of PR's by renovate; one for each package update. Merging those is a bit of a cumbersome task. We might want to consider grouping those.

In the light of recent supply chain attacks, I figured it would also be a good idea to not always bump directly to the latest version, so I also set minimumReleaseAge to 2 days.

I am not too familiar with renovate, so not sure if everything still works exactly as intended. :)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[mkniewallner]

I'm ok with grouping PRs and auto-merging some to reduce the maintenance burden, but I would really prefer to not auto-merge major versions, as they could have breaking changes that could not be detected by the CI, even with high test coverage.

Even a dev dependency for instance could have breaking changes worth checking, where the CI could be green, but because an option is updated, the expected behaviour is changed without the CI telling you about it.