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 agentic-review-benchmarks#12

[sentry]

Bug: The notlike() filter for metadata is missing the escape="\\" parameter, causing incorrect results when searching for values containing special characters like % or _.
_{Severity: MEDIUM}

Suggested Fix

Add the escape="\\" parameter to the notlike() method call on line 1207 to ensure that special characters in the search value are correctly handled, consistent with other LIKE-based filters in the function.

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 "not contains" metadata filter at
`api/core/rag/retrieval/dataset_retrieval.py:1207` uses `notlike()` without the
necessary `escape="\\"` parameter. While other similar filters in the same function
correctly include this parameter to handle special characters, its omission here will
cause incorrect filtering behavior. When a user performs a "not contains" search for a
value that includes a special SQL character like `%` or `_`, the filter will fail to
correctly interpret the escaped value. For example, a search to exclude records
containing "50%" would not work as intended, leading to incorrect query results.

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