feat: improve @ file search for large projects

[daniel-lxs]

Summary

Simplified solution to #5721 - increases file search limit and respects VSCode search settings.

Changes

• Default limit: 5,000 → 10,000 (configurable up to 500,000)
• Respects VSCode search settings (useIgnoreFiles, useGlobalIgnoreFiles, useParentIgnoreFiles)
• Adds roo-cline.maximumIndexedFilesForFileSearch configuration
• Includes test coverage

Design

Conservative default (10k files) with opt-in for power users. No caching complexity - ripgrep is fast enough for on-demand searches.

Memory impact:

• 10k files: ~2-3MB (default)
• 50k files: ~10-15MB
• 500k files: ~100-150MB (max, user opt-in)

Alternative to PR #5723

This PR solves the same issue with 140 lines vs 2,200+ lines. Ripgrep's performance (<1s for 50k files) doesn't justify the maintenance burden of complex caching.

Closes #5721

---

Important

Enhances file search by increasing the default limit, respecting VSCode settings, and adding a configurable option, with test coverage included.

• Behavior:
  • Increases default file search limit from 5,000 to 10,000, configurable up to 500,000 in file-search.ts.
  • Respects VSCode search settings (useIgnoreFiles, useGlobalIgnoreFiles, useParentIgnoreFiles) in file-search.ts.
  • Adds roo-cline.maximumIndexedFilesForFileSearch configuration in package.json.
• Testing:
  • Adds tests in file-search.spec.ts to verify configuration integration and default limit behavior.
• Misc:
  • Adds multilingual descriptions for maximumIndexedFilesForFileSearch in various package.nls.*.json files.

^{This description was created by for ab7e566. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Review Summary

I've completed the review of this PR. The implementation looks solid - increasing the file search limit and respecting VSCode search settings is a good solution for large projects. The latest commit adds translations correctly across all supported languages.

Issues Found

• Test Implementation: The tests in file-search.spec.ts don't actually verify behavior. They only check that mocks are defined rather than validating that the correct ripgrep arguments are passed based on VSCode configuration settings.

Code Review Notes

Positive aspects:

• Configuration changes are well-structured with appropriate min/max limits (5,000 - 500,000)
• Default increase from 5,000 to 10,000 is conservative and reasonable
• The implementation correctly respects VSCode's search settings (useIgnoreFiles, useGlobalIgnoreFiles, useParentIgnoreFiles)
• getRipgrepSearchOptions() properly translates VSCode settings to ripgrep flags
• The limit parameter in executeRipgrepForFiles correctly falls back to the configured value
• Translation additions in commit 9070ff4 are complete and consistent across all languages

Areas of concern:

• Test coverage doesn't provide actual verification of the new functionality

Follow Along on Roo Code Cloud

[roomote]

Review complete. Found 1 issue that should be addressed before merging.

[roomote]

Review complete. The translation additions are correct and the core implementation is solid. However, I cannot approve until the test implementation issue is addressed.