Amplify status check fails with Github Merge Queue

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d2t0beklulssyh

### AWS Region

us-east-1

### Amplify Hosting feature

Backend builds, Build settings, Git providers

### Frontend framework

React

### Next.js version

N/A

### Next.js router

N/A

### Describe the bug

When enabling a github Merge Queue https://github.blog/2023-07-12-github-merge-queue-is-generally-available The github app that builds the pull request fails to build the app for the pr on the queue.

### Expected behavior

I expect the build to succeed and the pr to automatically merge after the status is reported success.

### Reproduction steps

1. Enable Github Merge Queue
2. Create a pull request

### Build Settings

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

No file, test, or log entry point is named. Start by reproducing the failure with GitHub Merge Queue and an Amplify Hosting build, then trace how the pull-request build status is reported. Done means the queued pull-request build succeeds and reports a successful status so the pull request can merge automatically.

Written by the indexing model from the issue text.