Escape comment value in JDBC connectors

[ebyhr]

Description

Fixes #14058

Release notes

(x) Release notes are required, with the following suggested text:

# ClickHouse
* Fix query failure when adding a column with a column comment which has special characters which require it to be escaped. ({issue}`14058`)

# ClickHouse, MariaDB, MySQL, 
* Fix query failure when creating a table with table or column comment which has special characters which require it to be escaped. ({issue}`14058`)
* Fix query failure when setting a table comment which has special characters which require it to be escaped. ({issue}`14058`)

# ClickHouse, Oracle, PostgreSQL, Redshift
* Fix query failure when setting a column comment which has special characters which require it to be escaped. ({issue}`14058`)

[findepi]

(skimming)

[findepi]

I am not sure there is much benefit of using the prepared statement for the comment.
it's nice, but we still need to know how to escape all the other stuff (table name, column names, check constraints (in the future), etc). Escaping the COMMENT value isn't any harder that what we do today.

[ebyhr]

In case of MariaDB, they have NO_BACKSLASH_ESCAPES (global & session) property. If we escape the comment without respecting the property in our side, the inserted comment might be different from what we specified in Trino DDL. Also, I guess there're other cases we are missing. That's why I introduced prepared statements in this PR.

[findepi]

We control the MariaDB connection (session), so we should force NO_BACKSLASH_ESCAPES to be true.
This is important for complex predicate pushdown as well, see RewriteVarcharConstant.

[ebyhr]

Reverted prepared statement change. Do you want me to force NO_BACKSLASH_ESCAPES in this PR?

[findepi]

We can do this as a follow up (It's a "minor correctness" problem. We just don't properly support comments with backslashes.)

[findepi]

It's better to have addition of surrounding ' and escaping intra-value ' in a single place.

comment.map(PostgreSqlClient::varcharLiteral).orElse("NULL")

private static String varcharLiteral(String value) {
{
   return "'"  + value.replace("'", "''") + "'";
}

[findepi]

BTW this is SQL-standard behavior, it doesn't need to be implemented in this class, i.e. every conformant DB should behave like this, so it can be provided by the base-jdbc

[findepi]

Added this in the test