Fix bash tool isError behavior to match taiga implementation

- Changed bash tool to always return isError=false for successfully executed commands
- Non-zero exit codes are part of normal command output, not MCP protocol errors
- Only actual tool execution failures (exceptions) now set isError=true
- This aligns with taiga's bash tool behavior where CLIResult contains output/error but doesn't set isError based on exit code

Author: Keno

src/tools/bash.jl

@@ -87,9 +87,9 @@ function execute(tool::BashTool, params::Dict)
 
         result_text = join(response_parts)
 
-        # Command had non-zero exit code, treat as error
-        is_error = exit_code != 0
-        return create_content_response(result_text, is_error=is_error)
+        # Return success - non-zero exit codes are part of normal command output, not MCP errors
+        # Only actual tool failures (exceptions) should set isError=true
+        return create_content_response(result_text, is_error=false)
 
     catch e
         error_msg = "Failed to execute command: " * string(e)