bug: 2.0 changed command names

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

linux

### Expected behaviour

hook scripts written against 1.x continue to work

### Actual behaviour

1.x:
```
{"hook_event_name":"preToolUse","cwd":"/home/jjshoe/wickfire/iac","session_id":"752f697f-8e63-4de7-bab9-2d5d1597c4a6","tool_name":"write","tool_input":{"command":"str_replace","oldStr":"b","newStr":"c","path":"/tmp/a"}}
```

2.0

```
{"hook_event_name":"preToolUse","cwd":"/home/jjshoe/wickfire/iac","session_id":"752f697f-8e63-4de7-bab9-2d5d1597c4a6","tool_name":"write","tool_input":{"command":"strReplace","oldStr":"b","newStr":"c","path":"/tmp/a"}}
```

No note was added to the changelog about this, and this breaking change then allowed my agent to go nuts since I use a hook against the tool_name of write to stop kiro from making rogue unasked for edits, it immediately started running amok on my system

### Steps to reproduce

_No response_

### Environment

```yaml

```

Beginne damit, die Hook-Payload unter Linux mit q doctor und q restart zu reproduzieren, und verfolge dann den CLI-Pfad, der preToolUse-Felder wie tool_name und tool_input.command ausgibt. Als abgeschlossen gilt die Aufgabe, wenn Hook-Skripte, die für 1.x geschrieben wurden, den Befehlsnamen weiterhin erkennen und das Kompatibilitätsverhalten durch einen geeigneten Test abgedeckt oder als Breaking Change dokumentiert ist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.