Description

This PR refactors the global search functionality and moves it mostly to the main process. This is done by creating a new provider for searches. The reason for this is that this allows us to implement stateful logic, including caching. This can allow us to provide better search experiences in the future which rely on pre-computed data (incl. vector search or BM25-variants).

Changes

Two crucial functions of the full text search have been removed from the renderer and moved to the new Search Provider: The compile-search-terms function and the actual searching action.

In addition, the entire search has been overhauled:

• Clearly label it as a "boolean search" now
• Fixed an issue that would finish a search in a file when all search terms were matched immediately. This would foreclose later matches in the same file.
• Now searches are by default done only case-insensitive. Previously, the search would run twice, once in regular case, one in lower case. This cuts search times on average in half.
• Users can now specify whether they want to actually run a case sensitive search.
• Improved the terminology used throughout the search
• Removed a bunch of odd and messy choices
• Improve the search by combining results from the same file on the same line
• No longer just provide the entire line as a result; instead now a window around the search match(es) is returned of about 40 characters by default, which can include additional context information
• Moved some of the types of the search around to collocate them with the corresponding providers
• Modularize the search to allow for the inclusion of different types of search in the future

Additional information

There currently still one iffy thing I'd like to address before merging: I found out while benchmarking that the search now is blazingly fast (good!) but this doesn't appear like such with the user, because the Vue reactivity adds so much overhead that a search that takes 0.5s visually takes ca. 4-5s until all elements are processed and rendered. There is lots of room for performance improvements here.

AI Disclosure Statement

No AI has been used whatsoever in crafting this PR. (The search functionality was all over the place and is many years old at this point, I think an AI would've had a hard time improving that as fast as I did.)

Tested on: macOS Tahoe 26.5