Amplify App - entire app - unwanted disappearance, and not deleting completely when actually deleting.

### 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

dyyvoq47s0kba

### AWS Region

us-west-1

### Amplify Hosting feature

Deployments, Not Applicable

### Describe the bug

- About 10 days ago we had an entire Amplify app disappear from the "All Apps" Section in Amplify after leaving the Amplify console up for an extended period of time, then logging back in. We shrugged it off thinking it was our mistake. Linked to the "original" GitHub account. We then setup an Amplify App, which worked.
- A few days ago, we created a new Amplify app and deleted the old one and linked to a different temporary GitHub account. No issues at all.
- Earlier today, we decided get rid of that working Amplify App as we needed to connect back to the "original" GitHub account. After deleting the app, and some navigating around, the Amplify App from a few days ago **reappeared** in our Amplify Apps. Keep in mind we deleted this one already. We redeleted it, and created a new Amplify app connected to the "original" GitHub Account - the original intention of today. We received the error "CNAMEAlredyExistsException". Waited an hour, not working. It says in the supporting docs to then wait 6 hours. We did so; the issue still persisted.
- Just now, after 6 hours of waiting for any previous source to be unlinked and linking domains was still not working, we tried deleting the app that we created earlier today and create a new, fresh one. Did so, opened a new window and moved that window to my other monitor, and after refreshing the Amplify Apps, the App from a few days ago appeared **again** and the Amplify App I just created - it was in the process of running the build - disappeared. It seems like deleting an app does not work properly, and also leaving sessions open for too long or creating 2 windows for the Amplify App is prone to complete deletion of any previous progress which is very frustrating.

### Expected behavior

Amplify Apps should be completely deleted when you delete.
Previously deleted Amplify Apps should not reappear.
Amplify Apps should not delete themselves after extended sessions in the console or after creating a new window and moving to another screen.

### Reproduction steps

I'm not sure if this is a guarantee, but try
1. Create an amplify app like normal. Link to a github repo.
2. Wait until it auto logs you out due to timeout. **See if the app is deleted.**
3. If it's not, delete the app.
4. Create a new app linked to the same Gihub repo.
5. Duplicate the window and move to another screen.
6. On the duplicated screen, refresh the page and login out and back in. Do this a few times.
7. Go back to the original window and refresh. **See if the app you just deleted reappears.**

### Build Settings

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

Start by reproducing the reported workflow in the Amplify console: create and delete apps, wait for session timeout, duplicate the window, refresh, and log out and back in. Compare the All Apps list and deletion results against the expected behavior: deleted apps stay gone, new apps do not disappear, and the workflow does not leave CNAME conflicts.

Written by the indexing model from the issue text.