fix: escape control characters in native TCP query parameters

[Laotree]

String parameters containing tab, newline, CR, backslash, or NUL were silently truncated when sent via the native TCP protocol. The server decodes parameter values through two stages — readQuoted then deserializeTextEscaped — so control characters must be double-encoded by the client. Replace the single-quote-only ReplaceAll in encodeFieldDump with a strings.Replacer that handles all special characters correctly.

Fixes #1792

Summary

Checklist

Delete items not relevant to your PR:

• Unit and integration tests covering the common scenarios were added
• For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

[github-actions]

Summary

This PR fixes a real bug: string query parameters containing tab, newline, CR, backslash, or NUL were silently truncated when sent over the native TCP protocol because the server runs parameter values through two decode stages (readQuoted then deserializeTextEscaped), but the client only escaped single quotes. The fix is correct — replacing the single strings.ReplaceAll with a package-level strings.Replacer that double-encodes all special characters. The encoding logic and its comments are accurate and clear, the unit tests are table-driven and well-constructed, and the README addition is a welcome improvement. The approach is sound.

Should fix

1. No HTTP protocol integration test. The review checklist requires coverage for both TCP and HTTP. The HTTP path encodes parameters as URL query params (a separate code path untouched by this PR), so the bug never affected it — but a test confirming special characters round-trip correctly over HTTP would catch any future regression and satisfy the checklist. Consider adding an HTTP variant in tests/issues/1792_test.go using GetConnectionHTTP (or the equivalent) with the same case table.

2. No database/sql (std API) integration test. The checklist requires coverage for both the native Open() API and the database/sql OpenDB() API. Adding a Test1792Std that exercises sql.Named parameters with the same special characters via the std shim would complete the coverage.

Nits

• nit: t.Skip(fmt.Errorf("unsupported clickhouse version")) wraps a string in an error solely to pass it to t.Skip, which accepts ...any. Prefer t.Skipf("unsupported clickhouse version") — it reads more naturally and matches the pattern used elsewhere in the test suite.
• nit: The return immediately after t.Skip(...) is unreachable — t.Skip calls runtime.Goexit() internally. It's harmless but can be dropped.

Verdict

Request changes — the fix and unit tests are correct, but HTTP and std API integration test coverage is missing per the project checklist.