chore: improve dependabot config publish weekly with groups

[jedevc]

Follow-up on comments from #6352 (comment).

Getting kinda annoyed with all the dependabot spam 😢

• By moving from once-a-month to once-a-week, we stay more on top of changes, which means there should be fewer to address all at once. Additionally, I've set the time to trigger on Monday morning - that way, we can hopefully review and merge before the next release.
• I've also used groups to try and ensure that each set of updates is all combined, so we don't get a complete overflow of updates. Unfortunately, we don't seem to be able to combine all the go updates together (see Support for grouped update PRs that group across directories with same ecosystem dependabot/dependabot-core#7547) - so we may still get invalid PRs, since the go.mods interact with each other in fun ways.
• Finally, I've removed the version-update:semver-patch from Go - at least for the core engine+components, I'd like to try following patch updates as well. Some projects follow semver a little differently (even though ideally they wouldn't 😆), and I'd like to make sure we don't fall behind.

[gerhard]

I'm open to trying this new config out 👍 🚀

FTR:

• tooling: Reduce frequency of Dependabot PRs #5099