ci(mergify): upgrade configuration to current format

[mergify[bot]]

[!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?

• pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (deadline: 2025-01-31)
• pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (deadline: 2025-01-31)
• pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (deadline: 2025-01-31)

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! 🎉

[mergify[bot]]

This pull request's title should follow requirements next. @mergify[bot] please check it :point_down:.

Valid format:

fix(vc): fix sth..... (#3306)
  ^         ^---------^  ^----^
  |         |            |
  |         +            +-> you issue id.
  |         |
  |         +-> Summary in present tense.
  |
  +-------> Type: feat, fix, docs, workflow, style, refactor, test, website, chore

Valid types:

• feat: new feature for stonedb
• fix: bug fix for stonedb
• docs: changes to the documentation
• workflow: ci/cd in .github
• perf: Changes to improve code performance
• refactor: refactoring production code, eg. renaming a variable
• style: formatting, missing semi colons, etc; no production code change
• test: adding missing tests, refactoring tests; no production code change
• website
• chore: updating grunt tasks etc; no production code change

[mergify[bot]]

Thanks for the contribution! I have applied any labels matching special text in your PR Changelog.

Please review the labels and make any necessary changes.