Request user confirmation for actions that interrupt the current flow

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

Prevent accidental interruption of the current flow

### Proposed solution

Requesting the user a confirmation before executing actions that can potentially interrupt the current work flow (i.e. quitting the CLI, canceling the clarifying questions form filing process, etc).

Users (like me) that are so used to some of the Copilot keyboard shortcuts doing something else in terminals (i.e. C-d to delete the next char) should benefit for it.

### Example prompts or workflows

The following example shows the scenario that made me file this issue after hitting the third "C-d loop" iteration in a row 😄:

1. The user issues a prompt in plan mode
2. Copilot asks clarifying questions and requires a form to be filled
3. While editing the form, the user intends to delete the next char of the current word and types C-d
4. Copilot dismisses the form
5. The user needs to issue another prompt asking Copilot to recover the form filing process
6. Goto step 2 and hope for the best 😄

### Additional context

_No response_

The issue identifies the CLI quit path and the clarifying-questions form flow as interruption points; start by tracing how those actions are triggered from terminal input. Add confirmation before quitting or dismissing active work, and verify that accidental shortcuts no longer discard the current flow.

Scritto dal modello di indicizzazione a partire dal testo della issue.