[Search] Cannot find pages with direct search term presence in edge cases

Nobody has claimed this yet.

### Search first

- [X] I searched and no similar issues were found

### What Happened?

## Demo

- Search term «really issu» has no results at all, but should have
- Search term «really issu**e**» has the only one result item, but page with words «really» and «issue» hasn't been found

Logseq couldn't find exact page in graph. From my point of view this is really **serious** issue, as it is not obvious (like an app crash for example)

### Reproduce the Bug

1. Create a reference to the page with name: «this is the page and its name is very long — so long, that final words cannot be found in logseq search and this is a REALLY big issue»
2. Open search (cmdk) & try to find by search term «really issu» — no results
3. Open search (cmdk) & try to find by search term «really issue» — one result, but the page with exact match is missing

### Expected Behavior

Pages with exact words match should be found

### Screenshots

_No response_

### Desktop or Mobile Platform Information

MacOS v13.4
Logseq Desktop v0.10.8

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

No file or test is named. Start by reproducing the issue in Logseq Desktop with the supplied long page title and search terms, then trace the search entry point and matching logic. Done means both “really issu” and “really issue” find the page containing the exact words.

Written by the indexing model from the issue text.