[jdbc-v2] JDBC Escaping

### Description
JDBC escaping allows to write portable (really not) SQL statements that can be run with different JDBC drivers to get same affect. For example, `{ts 2025-02-20}` should be interpreted by driver as native function like `toTimestamp()` and other drivers should do similar way.

Current JDBC implementation
- does escaping always but should be controlled by `com.clickhouse.jdbc.StatementImpl#setEscapeProcessing`
- should be true for both Statement and PreparedStatement with according tests
- lacks of documentation https://clickhouse.com/docs/integrations/language-clients/java/jdbc
- done after prepared statement is parsed but should before (to not confuse parser :-))

There is a good explanation of how JDBC escaping works https://jdbc.postgresql.org/documentation/escapes/.

Start with com.clickhouse.jdbc.StatementImpl#setEscapeProcessing and trace how escaping is applied relative to prepared-statement parsing. Review the JDBC escaping explanation and the JDBC integration documentation, then add coverage for both Statement and PreparedStatement. Done means escaping is configurable, enabled for both statement types, and documented.

Written by the indexing model from the issue text.