Incorrect results with the search box

### What happened?

The documentation says that the search box looks for the text in the title: https://allurereport.org/docs/sorting-and-filtering/#filter-tests-by-name

I noticed that it also looks in other things like the links or the error messages (which is really useful, thank you for that!)

But it is rather inconstistent and sometimes shows result that do not match the text searched

### How can we reproduce it?

My test:
```js
test.describe("Device Sheet", async () => {

test.beforeEach(async () => {
await allure.parentSuite("One");
await allure.suite("Two");
await allure.subSuite("Three");
});

test.only("this test fails", async () => {
await allure.label("Criticity", allure.Severity.NORMAL);
await allure.link("JIRA-819", "JIRA-819");
await allure.step("step", async () => {
await expect(1, "1 should equal 4").toBe(4);
});
});
});
```
run with `npx allure run npx playwright test ` and then `npx allure open`

1. Search for anything present in the test `titlePath` -> the test shows in the results 🆗

2. Search for "equal" -> the test shows in the results (matches the error message, should not be OK but really useful!)

3. Search for "Two" -> the test shows in the results (matches the suite, should not be OK but really useful!)

4. Search for "One" -> No result (doesnt match the parentSuite, inconsistent with 3.)

5. Search for "Three" -> No result (doesnt match the subSuite, inconsistent with 3.)

6. Search for "jira-819" -> the test shows in the results (matches the link, should not be OK but really useful!)

7. Search for "jira-8129" -> the test shows in the results (matches the link even though it is a different text, ❗ )

### What did you expect?

Having the search box look for the text in more than just the titlePath was a really good surprise, my team uses the search with error messages and links on a daily basis, it is a really good addition.

I just wished it looked for an exact match in a contains rather than a fuzzy search (ie it would match the test with a "819" search in the example above, but not with a "8129"

### Environment

- Allure 3 version: 3.17.0
- Node.js version: v22.11.0
- Playwright version: 1.63.0

### Additional context

_No response_

Reproduce the issue with the provided Playwright test, `npx allure run npx playwright test `, and `npx allure open`; start by tracing how the report search box matches test data. Compare exact substring matching with the examples for `819` and `8129`, and verify that searches for suite names, error text, and links behave consistently.

Written by the indexing model from the issue text.