ci: remove bot account from default queue

[black-dragon74]

Describe what this PR does

This PR removes the bot account from default queue in mergify rules.

[mergify]

Merge Protections

🟢 All 2 merge protections satisfied — ready to merge.

Show 2 satisfied protections

🟢 📃 Configuration Change Requirements

Mergify configuration change

• any of:
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

[nixpanic]

/queue

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.37/nfs

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.35

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.35

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.34

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.36

[ceph-csi-bot]

/test ci/centos/upgrade-tests-cephfs

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.34

[ceph-csi-bot]

/test ci/centos/upgrade-tests-rbd

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.36

[mergify]

queue

🛑 This pull request comes from a fork and cannot be rebased on behalf of a user

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing a fork's pull request on behalf of a GitHub user means impersonating that user to force-push the contributor's branch. Mergify does not do that.

Unset update_bot_account on the default queue to keep queueing pull requests from forks: with no account to impersonate, the update rebases through GitHub's API as Mergify, which the installation token is allowed to do. A fork pull request that changes GitHub Actions workflows, or that another GitHub App's bot opened, is the exception: GitHub lets Mergify queue one in place only with an update_bot_account, so a queue that receives those has to run its checks on a draft pull request instead. So is one that changes more than 3000 files: GitHub stops listing a pull request's files there, so Mergify cannot rule out a workflow change and treats it as one. update_method: merge works too, and merges the base branch into the pull request rather than rebasing it.