Prepare Repository for Merge Queue

[opajonk]

• Add Overall Result job which depends on all required status checks
• Add merge_group event

[JP-ETAS]

You could make a new workflow merge-queue.yaml and call this workflow from that one. This would mean you don't need your overall-result job as you could just use the merge-queue.yaml workflow status directly.

Would also be clear in the code if someone wanted to extend the merge queue tests in the future

[opajonk]

I must say I am not a fan of workflows including workflows... it just starts to be convoluted really quickly, and I need to jump between files when editing, think about branches, etc.

Here, I'd argue the workflow is really short enough and we should not use multiple files.

We can discuss the naming of the steps, though. I am not entirely happy yet. I like solutions like described here. What do you think?

[opajonk]

OK, admittedly it is possible to omit the branch ref if it is in the same repository. And it should probably be done almost always, unless one wants to run into weird issues. But again - here, the workflow is so short... why add complexity.