ci(mergify): upgrade configuration to current format

[mergify]

No more deprecated fields are being used in your Mergify configuration, this pull request will be closed.

[mergify]

Merge Protections

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

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

• check-success = Configuration changed

[github-actions]

Pull Request Review

This is a diff file that shows the changes made to the .github/mergify.ym�[19D�[K .github/mergify.yml` file in a pull request. The changes are as follows:

• The actions section has been modified to include a new action named me�[3D�[K merge`.
• The method attribute of the merge action has been changed from squas�[6D�[K squashtorebase`.
• A new section named merge_protections_settings has been added, with a s�[1D�[K
  single attribute named reporting_method set to check-runs.

This change is likely intended to update the mergify configuration file to �[K
use the rebase method for merging pull requests instead of squashing them. �[K
The merge_protections_settings section is used to configure merge protect�[7D�[K
protection rules for a repository, and the reporting_method attribute det�[3D�[K
determines how merge conflicts are reported when a pull request is merged.

The diff file also includes a new line numbered 6,5, which suggests that th�[2D�[K
there may be additional changes to the file beyond those shown in the diff.�[5D�[K
diff. It's possible that other developers have made changes to the file sin�[3D�[K
since the last commit was made, and these changes are not reflected in the �[K
diff file.

[github-actions]

ubuntu-latest

This is a diff of a file named .github/mergify.yml. The file contains con�[3D�[K
configuration settings for the Mergify bot, which is used to manage pull re�[2D�[K
requests in GitHub repositories. The changes made to the file are as follow�[6D�[K
follows:

• Line 6: The actions section was added to define the merge method for pu�[2D�[K
  pull requests. The merge_protections_settings section was also added to d�[1D�[K
  define the reporting method for check runs.

[github-actions]

Pull Request Review

This is a diff file for Git. It shows the changes between two versions of �[K
a file, specifically the .github/mergify.yml file in this case.

The diff has three sections:

1. diff --git: This line indicates that the diff is for a Git file.
2. index 0e6436c..1f93e75 100644: This line shows the old and new version�[7D�[K
   versions of the .github/mergify.yml file, with the commit hashes and file�[4D�[K
   file permissions (100644 in this case).
3. pull_request_rules: actions: merge: method: squash merge_protections_se�[20D�[K merge_protections_settings: reporting_method: check-runs: This line shows �[K
   the changes made to the .github/mergify.yml file, specifically adding a n�[1D�[K
   new section called merge_protections_settings with the value reporting_m�[12D�[K reporting_method: check-runs`.

In summary, this diff file indicates that a new section has been added to t�[1D�[K
the .github/mergify.yml file in the form of merge_protections_settings,�[29D�[K
merge_protections_settings, and its value is set to check-runs.

[github-actions]

windows-latest

This is a diff of the file .github/mergify.yml between two commits. The di�[2D�[K
diff shows that there are three changes made to this file.

Here's a summary of the changes in bullet points:

• The pull_request_rules section has been updated, with a new action call�[4D�[K
  called "merge" added to the actions list. This action uses the "squash" m�[1D�[K
  method for merging pull requests.
• A new section called merge_protections_settings has been added to the f�[1D�[K
  file, which specifies that check-runs should be used as the reporting metho�[5D�[K
  method for merge protection failures.

[github-actions]

Pull Request Review

This diff file shows the changes made to the .github/mergify.yml file in�[2D�[K
in the repository. The changes are related to the pull request rules, speci�[5D�[K
specifically the actions for merging and the settings for merge protection.�[11D�[K
protection.

Here's a breakdown of the changes:

• actions: This section defines the actions that can be taken on pull req�[3D�[K
  requests. In this case, it specifies that when a pull request is merged, it�[2D�[K
  it should be done using the squash method.
• merge_protections_settings: This section defines the settings for merge�[5D�[K
  merge protection, which helps prevent accidental merges or pushes to the ma�[2D�[K
  main branch. The reporting method specified here is check-runs, which wil�[3D�[K
  will create a check run on GitHub for each pull request that requires merge�[5D�[K
  merge protection.

Overall, this diff file shows how the .github/mergify.yml file can be use�[3D�[K
used to define the rules and settings for merging pull requests in a reposi�[6D�[K
repository.

[github-actions]

macos-latest

Here is a summary of the code diff in bullet points:

• The file .github/mergify.yml has been modified.
• The pull_request_rules section has been updated.
  • The actions section has been added or updated to include the merge me�[2D�[K
    method set to squash.
  • A new merge_protections_settings section has been added with the repor�[6D�[K reporting_methodset tocheck-runs`.