Merge queues rollout announcement

[webknjaz]

GitHub's merge queues gone GA a few months ago: https://news.ycombinator.com/item?id=36707239. They only work in orgs, not personal accounts.

I'm enabling them in some repos in the aio-libs org.

This requires a GHA change like aio-libs/aiomonitor@0d64f22 (in cases when there's catch-all push triggers, they should also exclude temporary read-only branches).
Then, it needs to be enabled in the branch protection.

The only thing I change from the defaults is unchecking the following setting:

• Only merge non-failing pull requests

So far, this is active in aiomonitor and aiohttp.

cc @achimnol @jettify @Nothing4You @Dreamsorcerer @mjpieters @aio-libs/admins

[webknjaz]

@Dreamsorcerer please, pay special attention to backports of PRs merged via Merge Queues. I just want to verify that Patchback works as expected, since this scenario is largely untested.

Also, I wasn't able to enable merge queues on stable branches because, they don't work with pattern-based rules. Might add extra rules later on.

[webknjaz]

@Dreamsorcerer apparently, some integrations don't run checks for the merge_group event, so they don't report anything, which blocks merging:

[webknjaz]

The upstream bug: readthedocs/readthedocs.org#10021

[webknjaz]

The WIP app also has an upstream bug on the tracker: wip/app#546.

[webknjaz]

And I'll need to fix this in Chronographer myself, obviously.

[webknjaz]

I disabled this in aiohttp until the problems are addressed. We could probably disable WIP and drop RTD from required as a workaround. Then, upon fixing my app, I'll re-enable it.