ci(mergify): rename conditions to queue_conditions to fix in place checks

[aemada-aws]

Issue # (if applicable)

Closes #.

Reason for this change

The Mergify configuration currently uses the deprecated conditions key inside queue_rules.
Mergify now interprets conditions as merge_conditions, which unintentionally makes the setup a two-step CI.
This prevents in-place checks from working and causes conflicts with GitHub’s branch protection rule “Require branches to be up to date before merging.”

Response from Mergify team:

You still have a conditions key in your queue rules, which translate to merge_conditions since the conditions attribute is deprecated. Having merge_conditions in your queue rules makes it a 2-step CI.
You can see more details on inplace checks in our documentation: https://docs.mergify.com/merge-queue/parallel-checks/#inplace-checks-no-drafts

Description of changes

• Updated all queue_rules entries to use queue_conditions instead of conditions.

Describe any new or updated permissions being added

N/A — no IAM changes required.

Description of how you validated changes

• Only way to test is to merge it.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.