Ensure we always run ci on push for renovate and enable the merge group event trigger for merge queues

[Marcel-Nordeck]

This fixes the automerge things to get stuck for renovate and applies renovate's best practice to use merge queues. These are free for public repositories according to https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue

✔️ Checklist

• A changeset describing the change and affected packages (more info).
• Added or updated documentation.
• Tests for new functionality and regression tests for bug fixes.
• Screenshots or videos attached (for UI changes).
• All your commits have a Signed-off-by line in the message (more info).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 792cf6a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[HarHarLinks]

What about DCO, does it already run? Renovate seems to sign off alright, but it needs to pass the check.

Otherwise lgtm

[HarHarLinks]

I think this does not do anything relevant before #943, does it?

[Marcel-Nordeck]

yeah best after #943

[Marcel-Nordeck]

#943 is now done -> @HarHarLinks have another look please and apply the necessary settings :)