Refactor ACE tools to unify under 'ace-search' and update documentation

- Updated tool descriptions and usage in various prompts to reflect the new unified 'ace-search' tool.
- Removed individual ACE tool references (e.g., ace-find_definition, ace-find_references) and replaced them with 'ace-search' that supports multiple actions.
- Adjusted code handling in ToolResultPreview and MCP tool execution to accommodate the new unified structure.
- Enhanced comments and documentation for clarity on tool functionalities and usage.

Author: MayDay-wpf

docs/usage/en/05.Sub-Agent Configuration.md

@@ -161,7 +161,7 @@ You can create custom sub-agents through the configuration interface to meet spe
    - Press Space to select/deselect tools
    - Tool categories include:
      - Filesystem tools (filesystem-read, filesystem-create, filesystem-edit, etc.)
-     - ACE code search tools (ace-find_definition, ace-semantic_search, etc.)
+     - ACE code search tool (`ace-search` with action: find_definition / find_references / semantic_search / file_outline / text_search)
      - Codebase tools (codebase-search)
      - Terminal tools (terminal-execute)
      - TODO management tools

docs/usage/en/17.LSP Configuration.md

@@ -18,8 +18,8 @@ Snow CLI will try to use LSP first for certain code-search capabilities. If LSP
 
 Currently, LSP mainly enhances these built-in tools:
 
-- `ace-find_definition`: prefers LSP "go to definition"; falls back to regex search on failure
-- `ace-file_outline`: prefers LSP `documentSymbol`; falls back to regex search on failure
+- `ace-search` (action=`find_definition`): prefers LSP "go to definition"; falls back to regex search on failure
+- `ace-search` (action=`file_outline`): prefers LSP `documentSymbol`; falls back to regex search on failure
 
 Notes:
 
@@ -136,7 +136,7 @@ If you don’t want to install LSP for a language, remove its entry (or remove i
 
 ## Using LSP via ACE tools
 
-### 1) Go to definition: `ace-find_definition`
+### 1) Go to definition: `ace-search` (action=`find_definition`)
 
 If you provide `contextFile`, Snow CLI will try LSP first; otherwise it uses regex search directly.
 
@@ -147,13 +147,13 @@ It’s recommended to pass cursor position:
 
 Example: if your editor shows "Line 34, Column 7", you usually pass `line=33`, `column=6`.
 
-### 2) File outline: `ace-file_outline`
+### 2) File outline: `ace-search` (action=`file_outline`)
 
 For extracting symbols from a single file, Snow CLI tries LSP `documentSymbol` first and falls back to regex search.
 
 Tip:
 
-- For large files/projects, start with `ace-file_outline` to get a high-level map, then drill down.
+- For large files/projects, start with `ace-search` (action=`file_outline`) to get a high-level map, then drill down.
 
 ## FAQ
 
@@ -172,5 +172,5 @@ Common causes:
 
 ### 3. Inaccurate jumps / wrong results
 
-- Provide `contextFile + line + column` when calling `ace-find_definition`
+- Provide `contextFile + line + column` when calling `ace-search` (action=`find_definition`)
 - If `symbolName` appears multiple times in the file and you don’t pass position, Snow CLI will try the first occurrence, which may be inaccurate