Copilot CLI incorrectly selects the wrong authenticated GitHub account when pushing commits

### Describe the feature or problem you'd like to solve

Copilot CLI becomes confused when multiple GitHub accounts are authenticated (e.g., EMU + personal GitHub) and attempts to push using the wrong identity, causing 403 push failures until I manually run gh auth switch

### Proposed solution

Copilot CLI should automatically detect when a push fails due to insufficient permissions on the active account, then prompt the user to confirm an account switch inline, and retry the push using the correct authenticated identity, without requiring a manual gh auth switch command.

The /user switch doesn't recognize EMU accounts

### Example prompts or workflows

Prompt:
“Commit and push my changes.”

### Additional context

I regularly use two authenticated GitHub accounts in my daily workflow:
- GitHub EMU (corporate)
- GitHub.com personal (under Microsoft org)

Copilot CLI currently:

- Commits locally
- Attempts to push using the wrong account
- Fails with: “mmansour_microsoft does not have permission to push to microsoft/webui.git (403)”
- Detects another authenticated account but refuses to switch without manual intervention
- Requires me to run gh auth switch manually every time

This breaks the flow of “commit + push” automation and makes Copilot feel unreliable in multi‑identity setups.

Start by reproducing the commit-and-push workflow with multiple authenticated accounts, then compare the /user switch behavior with the gh auth switch command. Define how insufficient-permission failures should trigger confirmation, account selection, and retry. Done means the correct identity can be selected inline without manual account switching.

Vom Indexierungsmodell aus dem Issue-Text verfasst.