ci(mergify): upgrade configuration to current format

[mergify]

Caution

The transformed Mergify configuration is invalid or contains deprecated fields that should have been transformed.
The shared key in your configuration could be the cause, Mergify cannot know what is inside this shared key so it cannot modify it.
In order for the configuration to be valid, you will need to manually modify it.

---

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2025-01-31, otherwise your configuration will stop working.

What's Changed?

• queue_rules → disallow_checks_interruption_from_queues: This attribute has been replaced in favor of using priority_rules at the top-level of the configuration combined with the allow_checks_interruption key, also in the priority_rules.
  ⚠️ The transformed configuration simply removes the deprecated attribute. We recommend you to create the required priority rules, if needed, to replace this deprecated attribute to fit properly to your merge queue's behavior. (deadline: 2025-05-31)
• queue_rules → speculative_checks: The per-queue rule speculative checks has been replaced by a global maximum parallel check in order to improve the performance of test scheduling. (deadline: 2025-01-31)
• The implicit priority for the queue rules, that was based on their order, is going to be removed in favor of using priority_rules.
  This transformation aim to create priority rules, based on your existing queue rules, in order to keep the same priorities. If this priority change is not needed for you, you should not close this pull request until the deadline, otherwise it will be re-created again. (deadline: 2025-06-30)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉