merge queue: embarking master (c766212), #9992 and #10013 together

[mergify]

✨ Pull request #9992 which was ahead in the queue has been dequeued (for the following reason: checks failed). The pull request #10013 has been re-embarked. ✨

Branch master (c766212), #9992 and #10013 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #10013.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

• check-success = test-prod-node20 / launch-prod
• check-success ~= ci-app-lint
• check-success ~= test-prod-node20 / run-playwright
• -check-failure ~= ci-app-
• -check-failure ~= ci-slackbot-
• -check-failure ~= test-prod-node20 /
• check-success = test-prod-node20 / build-prod
• check-success ~= ci-app-launch-dev
• check-success ~= ci-app-test

Required conditions to stay in the queue:

• -check-failure ~= ci-app-
• -check-failure ~= ci-slackbot-
• -check-failure ~= test-prod-node20 /
• check-success ~= ci-app-launch-dev
• check-success ~= ci-app-lint
• check-success ~= ci-app-test

---
previous_failed_batches: []
pull_requests:
  - number: 10013
...

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c73cf5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR