ci: fix mergify configuration

[tiran]

Pull Request Description

What

PR #903 removed the mypy check and moved all checks to pre-commit. Update mergify configuration to require successful pre-commit, pkglint, and docs builds before a MR can be merged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 05160f9e-5212-4889-871d-8465342f46a5

📥 Commits

Reviewing files that changed from the base of the PR and between 41e04c0 and 2167f28.

📒 Files selected for processing (1)

• .mergify.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .mergify.yml

---

📝 Walkthrough

Walkthrough

The .mergify.yml automatic-merge rule was updated: the single check-success=mypy requirement was removed and replaced with three checks: check-success=pre-commit, check-success=pkglint, and check-success=readthedocs (the file comment references check.yaml). All other check-success requirements, including unit and E2E suites, remain unchanged. Lines changed: +4/-2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating the mergify CI configuration to reflect recent check consolidation.
Description check	✅ Passed	The description directly relates to the changeset, explaining the context (PR #903 removing mypy) and the specific updates to mergify configuration required checks.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}