fix: EXPOSED-909 Escape single quotes in locate() substring

[Alexandre Kohler (kwy404)]

Description

Summary of the change: locate() puts its substring argument inside a SQL string literal without escaping single quotes, so a substring such as ' or foo' produces invalid SQL. This PR escapes those quotes.

Detailed description:

• Why: Every dialect except Redshift writes substring straight into a quoted SQL string literal without escaping it. For example, stringLiteral("Joe's").locate("'") on H2 renders LOCATE(''','Joe''s'), which fails with a syntax error. The same happens with POSITION (PostgreSQL), INSTR (Oracle, SQLite) and CHARINDEX (SQL Server).
• What: The H2, MySQL, MariaDB, PostgreSQL, Oracle, SQLite and SQL Server locate implementations now double single quotes in substring, the same way RedshiftFunctionProvider.locate already does.
• How: One line per dialect, substring becomes substring.replace("'", "''"). Added testLocateWithSingleQuote to FunctionsTests. It fails before the change on all H2 modes (H2, MySQL, PostgreSQL, MariaDB, Oracle, SQL Server) and on SQLite with a SQL syntax error, and passes after it.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• Redshift
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

EXPOSED-909