bug: Multiple issues with Amazon Q CLI: fs_write errors and inefficient file search operations

### 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

### Operating system

Linux (Ubuntu/Debian-based distribution)

### Expected behaviour

Describe the bug
I'm encountering two issues when using Amazon Q CLI:

Frequent errors when trying to use the fs_write tool:
Amazon Q is having trouble responding right now:
0: failed to print tool, fs_write: No such file or directory (os error 2)
Location:
crates/chat-cli/src/cli/chat/mod.rs:1012

Inefficient file search: Amazon Q uses file enumeration instead of system search commands, which significantly slows down
operations.
Regression Issue

Select this option if this issue appears to be a regression.
Expected Behavior
The fs_write tool should work reliably without "No such file or directory" errors
When searching for files, Amazon Q should use system commands (find, grep, locate, etc.) for fast searching rather than
sequential file enumeration.

### Actual behaviour

Current Behavior
When trying to modify files, fs_write errors frequently occur, forcing me to use a workaround: creating a new file and renaming
it instead of direct editing.

When searching for files, Amazon Q "thinks" for a long time, going through files one by one instead of using system search
commands. When explicitly asked to use OS commands for searching, it starts using them and finds the necessary files almost
instantly.

### Steps to reproduce

Reproduction Steps
For fs_write error:
• Ask Amazon Q to modify the contents of an existing file
• Observe the "No such file or directory" error
• Suggest a workaround (create a new file and rename it)

For search issue:
• Ask to find a file in the system without specifying to use OS commands
• Observe long waiting time
• Ask to use find/grep/locate
• Observe instant results

Possible Solution
Fix path handling in the fs_write tool for correct operation with the file system
Optimize file search algorithms, using system search commands (find, grep, locate) by default instead of sequential enumeration
Additional Information/Context
These issues significantly reduce the efficiency of working with Amazon Q CLI. Workarounds exist, but they shouldn't be necessary
for basic functionality.

CLI version used
Amazon Q CLI (latest version)

Commencez par reproduire l’échec de fs_write et inspectez crates/chat-cli/src/cli/chat/mod.rs autour de la ligne 1012. Suivez ensuite le chemin de recherche de fichiers utilisé lorsqu’aucune commande de recherche de l’OS n’est demandée. C’est terminé lorsque les modifications de fichiers existants ne produisent plus l’erreur signalée et que les recherches de fichiers évitent le comportement séquentiel lent signalé ; vérifiez les deux cas de reproduction sur Ubuntu/Debian.

Rédigé par le modèle d'indexation à partir du texte de l'issue.