Renaming a GitHub repository backing an Amplify app means you cannot reconnect it

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

Build settings

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

At the moment, for AWS Amplify apps if you rename your repository for the given application, it is not possible to reconnect the application in Amplify. If you go to Monitoring -> Branch Settings -> Reconnect repository you will receive a toast popup error. You can reproduce this by simply renaming an existing repo backing an Amplify app, then trying to reconnect it.

This is different to another request which is to change the underlying repository completely:
https://github.com/aws-amplify/amplify-hosting/issues/4021

This issue is just specifically about renaming the existing repository on GitHub that backs the Amplify app.

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

1. Ideally, Amplify could understand when a repository has been renamed and automatically make the necessary changes to support the new name
2. If that's not possible, when you click Reconnect this works by updating the name to match the new repository name and updates any other references to the update repository name

Start in Amplify Hosting's Build settings flow, specifically Monitoring → Branch Settings → Reconnect repository, and reproduce the failure by renaming the backing GitHub repository. Done means reconnecting succeeds after the rename and updates the stored repository name and other references without requiring a different repository.

Written by the indexing model from the issue text.