fix(api): refactors the SQL LIKE pattern escaping logic to use a centralized utility function, ensuring consistent and secure handling of special characters across all database queries.

[tomerqodo]

Benchmark PR from qodo-benchmark#431

[sentry]

Bug: The notlike method call is missing the escape="\\" parameter, causing incorrect filtering when special characters like _ or % are used in a "not contains" filter.
_{Severity: MEDIUM}

Suggested Fix

Add the escape="\\" parameter to the notlike call on line 1207 to ensure the database correctly handles escaped characters. Change filters.append(json_field.notlike(f"%{escaped_value}%")) to filters.append(json_field.notlike(f"%{escaped_value}%", escape="\\")).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: api/core/rag/retrieval/dataset_retrieval.py#L1207

Potential issue: The code escapes special characters (`%`, `_`, `\`) for SQL LIKE
queries, but the `notlike` method call on line 1207 is missing the required
`escape="\\"` parameter. While other similar `like` and `ilike` calls in the same file
correctly include this parameter, its absence in the `notlike` call means the database
will not interpret escaped characters correctly. This causes "not contains" filters with
special characters to return incorrect results and introduces a potential wildcard
injection vulnerability.

_{Did we get this right? 👍 / 👎 to inform future reviews.}