About preview functionality bugs which seems have been fixed

### 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 questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

https://ap-northeast-2.console.aws.amazon.com/amplify/home?region=ap-northeast-2#/d2jveo7g4jys2l

### AWS Region

ap-northeast-2

### Amplify Hosting feature

Web previews

### Question

I have some questions about the bugs that seemed to have been fixed.

In the past, I was annoyed by certain issues, including the fact that resources (such as S3, Lambda@Edge, and CloudFront) were not deleted even after the preview was closed (issues #2424, #2273, and #2123).

Additionally, I noticed that the PR checks from GitHub remained "In progress" or “failed” when they failed and were redeployed in Amplify.
And cannot re-trigger builds with click the “re-run” button from GitHub (issues #367 #3287, #3261)

When I reached out to AWS support using a support case, they indicated that these issues seemed to have been resolved, but were not entirely certain.

Could you confirm whether or not these preview-related bugs have indeed been fixed?

No source files, tests, or entry points are named. Start by reviewing issues #2424, #2273, #2123, #367, #3287, and #3261 and comparing their current status with the reported AWS support guidance; done means a maintainer confirms whether each preview cleanup and GitHub check or re-run problem is fixed.

Written by the indexing model from the issue text.