Stale Edge Routing: Apex domain pointing to deleted app in different region after new app created

### 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 removed any sensitive information from my code snippets and submission.

### Amplify Hosting feature

Deployments

### Is your feature request related to a problem? Please describe:

**Describe the feature/bug**
After deleting an Amplify app and creating a new one with the same custom domain, the apex domain still routes to the old deleted app's load balancer in a different region. This is a stale edge routing issue that cannot be resolved through the console or by recreating the app.

**App ID:** d2oktj4sxkfk68 (us-east-1)
**Custom domain:** livingpatternsreadings.com
**Domain status:** Available

**Symptoms:**
- `www.livingpatternsreadings.com/about` results in 200 (correct -via CloudFront d3sbizcitmqxxw.cloudfront.net)
- `livingpatternsreadings.com/about` results in 404 (incorrect- from ip-10-124-5-46.us-west-2.compute.internal — old deleted app's ALB)

**Steps already tried:**
- Deleted and recreated custom domain multiple times
- Waited 24+ hours after domain status shows "Available"
- No apps exist in us-west-2 — old app is fully deleted
- Apex A records (3.33.251.168, 15.197.225.128) are locked/uneditable in GoDaddy and GoDaddy does not support ANAME/ALIAS

**Request:** Please manually clear the stale edge routing table entry for `livingpatternsreadings.com` so it points to the new app (d2oktj4sxkfk68, us-east-1) instead of the deleted app's us-west-2 infrastructure. Thank you very much

### Describe how you'd like this feature to work

The Amplify edge routing table should automatically update when a custom domain is removed from one app and added to a new app. When a domain shows "Available" status on a new app, all traffic (including apex) should route to that new app's infrastructure — not to a deleted app in a different region.

As a workaround for my immediate situation, I am requesting that an AWS engineer manually clear the stale edge routing entry for livingpatternsreadings.com so it points to app d2oktj4sxkfk68 (us-east-1).

The issue identifies Amplify Hosting custom-domain handling, the apex domain, CloudFront, an ALB, and app d2oktj4sxkfk68, but names no repository files, tests, or entry points. Start by locating the custom-domain edge-routing implementation and its tests, then determine how deletion and reassignment are represented. Done means the apex and www traffic both route to the newly assigned app after the old app is deleted.

Written by the indexing model from the issue text.