"Approve all file operations" should have a "this file only" option.

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

Create a new "Yes, and approve all edits to this file for the rest of the running session" option when editing files

### Proposed solution

When Copilot tries to edit a file, I am currently presented with three options:

```
1. Yes
2. Yes, and approve all file operations for the rest of the running session
3. No, and tell Copilot what to do differently (Esc)
```

Sometimes I want Copilot to be able to edit a file it just created iteratively but not touch any other files, or just keep track of which files it's touching, so I have to keep hitting option 1 for the entire session. There should be an option to approve all file operations on a per-file basis, so that Copilot can work independently but I can still monitor and gate which files it is accessing.

### Example prompts or workflows

"Create a new file called IMPLEMENTATION_PLAN.MD that will hold requirements for feature X"

Copilot:

```
Do you want to edit /Users/example/IMPLEMENTATION_PLAN.MD?

│ ❯ 1. Yes
│ 2. Yes, and approve all edits to this file for the rest of the running session
│ 3. Yes, and approve all file operations for the rest of the running session
│ 4. No, and tell Copilot what to do differently (Esc)
```