Allow switching to autopilot mode mid-task (restore pre-0.0.421 behavior)

[PrinceN1raj]

Describe the feature or problem you'd like to solve

Before version 0.0.421, I could switch from normal/interactive mode to autopilot mode using Shift+Tab while the agent was actively working on a task. This was critical for my workflow — I'd start a task in normal mode, review the agent's initial approach, and then switch to autopilot mid-task when I needed to step away (meetings, breaks, etc.). Autopilot would then handle ask_user questions and direct the agent autonomously. Since 0.0.421 (PR #3944), the autopilot permission dialog only appears on the next prompt submission, making it impossible to switch to autopilot during an active task. The mode change is essentially queued for the next prompt instead of applying immediately.

Proposed solution

Restore the ability to switch to autopilot mode mid-task via Shift+Tab (or the mode switcher)
so it takes effect immediately, even while the agent is actively working. The permission
elevation dialog can still appear — just show it at the moment of mode switch like before,
rather than deferring it to the next prompt. This could coexist with the current behavior: if
the user switches modes while idle, apply it on next prompt. If they switch while the agent is
active, apply it immediately.

Example prompts or workflows

1. I start a task in normal mode: "Refactor the auth module to use JWT tokens." The agent
   begins working and asks me questions. I review a few, then realize I need to leave for an hour.
   I press Shift+Tab to switch to autopilot — the agent continues autonomously, handling its own
   questions.
   ▎ 2. I submit a complex task in interactive mode to supervise the agent's plan. Once I'm
   confident in the direction, I switch to autopilot mid-task so it can finish without waiting on
   me for every file edit approval.
   ▎ 3. I'm working late and the agent is on a long task. I want to go to sleep but let the agent
   keep going. I switch to autopilot mid-execution so it won't block on ask_user calls overnight.

Additional context

The specific change that introduced this regression is in version 0.0.421, linked to PR
https://github.com/github/copilot-agent-runtime/pull/3944 — "Autopilot permission dialog appears
on first prompt submission instead of on mode switch." I've had to pin my CLI to version
0.0.420 to retain this workflow. I'm on Windows 11, using Copilot CLI via both VS Code terminal
and standalone terminal. This isn't an edge case — anyone who uses Copilot for longer tasks (30+
minutes) will likely encounter situations where they need to step away and switch to autopilot
mid-task. The current behavior forces users to predict upfront whether they'll be available for
the entire duration of a task, which isn't realistic.