ci(mergify): upgrade conf to use MP

[jd]

This implements a few changes:

• leverage MP to check for CI
• leverage MP to check for review requirements

[jd]

This pull request is part of a stack:

1. ci(mergify): upgrade conf to use MP (#6144) 👈
2. ci(mergify): implement priority rules (#6145)

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.

• all of:
  • check-success = lint
  • check-success = test
  • any of:
    • check-success = test-broken-links
    • label = ignore-broken-links
  • any of:
    • check-success=Cloudflare Pages
    • -head-repo-full-name~=^Mergifyio/

🟢 👀 Review Requirements

Wonderful, this rule succeeded.

• any of:
  • #approved-reviews-by >= 2
  • author = dependabot[bot]
  • author = mergify-ci-bot

🟢 Changelog requirements

Wonderful, this rule succeeded.

• any of:
  • -title ~= ^feat
  • label = need changelog
  • label = skip changelog

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.

• #changes-requested-reviews-by = 0
• #review-requested = 0
• #review-threads-unresolved = 0

[DouglasBlackwood]

Do we really need hotfix rules for the documentation?

[jd]

Do we really need hotfix rules for the documentation?

I thought about it, I'm not 100% sure but it's when you need it and you don't have it that you're unhappy. I think it's great to have this path of requiring a single approval if something's broken.

Pull request has been modified.