Add troubleshooting steps for the spawning of excessive rg processes #9950

Add troubleshooting steps for the spawning of excessive rg processes.

Users still regularly report the an excessive number of rg (ripgrep) processes are spawned. Looking closely at these reports, almost all of them show rg being executed with the --no-ignore flag. When run with this option, rg searches through directories like node_modules, which drastically increases the execution time. I suspect this happens because users do not understand the meaning of the Use Exclude Setting and Ignore Files button in the VS Code Search UI. With the toggle off, rg is executed with the --no-ignore flag.

Troubleshooting steps should advise users encountering this issue to:

1. Check the toggle button: Ensure that the "Use Exclude Settings and Ignore Files" button is enabled in the Search UI.
2. Verify your ignore settings: Confirm that search.useIgnoreFiles is set to true in your settings.
3. Disable symbolic link following: If the issue persists, setting search.followSymlinks to false may resolve it.
4. Set in settings.json:

{
  "search.exclude": {
    "**/node_modules/**": true,
    ".claude/worktrees/**": true
  }
}

Context:

• Repeated searches leaves orphaned, unkillable rg processes vscode#193927

• node_modules\@vscode\ripgrep\bin\rg is taking a lot of resources vscode#244376

• The rg process uses a huge amount of CPU. vscode#300132

• 1.113.0 regression: unbounded ripgrep processes freeze macOS when worktrees exist vscode#305544