Ask for confirmation before clearing chat history

[GoodluckH]

Sometimes users may habitually type /clear to clean the console output but in q chat, this actually erase chat history.

Adding a confirmation dialog to prevent mistakes.

Screen.Recording.2025-04-10.at.4.10.38.PM.mov

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 70.45455% with 13 lines in your changes missing coverage. Please review.

Project coverage is 13.98%. Comparing base (43f666f) to head (63f853d).

Files with missing lines	Patch %	Lines
crates/q_cli/src/cli/chat/mod.rs	70.45%	13 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1180      +/-   ##
==========================================
+ Coverage   13.46%   13.98%   +0.51%     
==========================================
  Files        2346     2364      +18     
  Lines      201210   204636    +3426     
  Branches   181574   185000    +3426     
==========================================
+ Hits        27091    28611    +1520     
- Misses     172822   174620    +1798     
- Partials     1297     1405     +108     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brandonskiser]

We definitely shouldn't duplicate this - if anything, add an extra parameter to the ChatState::HandleInput enum stating we are in the middle of clearing state.

[GoodluckH]

refactored

[brandonskiser]

This error message doesn't make much sense imo, this is just prompting the user regardless of whether or not tools are being presented.

[GoodluckH]

removed

[brandonskiser]

Previously this logic would just bubble up errors or return an exit state, so now we have to handle errors when instead it would be nicer to just have:

let input = match self.read_user_input(...)? {
Some(input) => input,
None => return ChatState::Exit
}

Prevents us from now handling errors verbosely in multiple locations.

Essentially change this to return a Result<Option<String>, ChatError> instead

[GoodluckH]

You're right! This is much cleaner now