Repo rename on GitHub breaks "My work" PR/issue filter semi-permanently

### Short summary

When a GitHub repository is **renamed**, the Copilot app keeps using the old `owner/repo` name when filtering PRs and issues. Removing and re-adding the repository doesn't help, since the app seems to derive `owner/repo` from the local clone remote URL.

### Affected version or release

1.0.16

### Installation context

GHE / Proxima, but likely affecting all GitHub flavors

### What happened?

When a repository is renamed in GitHub, in the Copilot app under "My work":
- The repository dropdown shows the old name.
- Selecting it (or "All repositories") shows **no** PRs/issues for the renamed repository.
- The stale name persists even after **removing and re-adding** the repository, because the app seems to use the local git remote URL to derive the filter value.

Note that the repository name is shown correctly in the app sidebar, as well as in settings. This seems to only affect the PR/issue view.

### Steps to reproduce

1. Clone `owner/old-name` locally and add it to the Copilot app.
2. Rename the repository on GitHub to `owner/new-name` (GitHub sets up a redirect; the local remote URL still points at `old-name` and keeps working).
3. Open **My Work** and use the repository filter dropdown.

### Expected behavior

The filter uses the repo's **canonical** current name (`owner/new-name`) and shows the current PRs/issues.

### Additional context

As a workaround, deleting the local clone or editing its remote URL to match the new clone URL, then removing and re-adding the repository fixes it.

Commencez dans le filtre de dépôts My Work de l’application Copilot et suivez la manière dont l’URL du remote git local devient la valeur du filtre PR/issue. Reproduisez le renommage de owner/old-name en owner/new-name, puis vérifiez que le filtre utilise owner/new-name et affiche les PRs et issues actuels du dépôt renommé.

Rédigé par le modèle d'indexation à partir du texte de l'issue.