Fix LowCardinality(Nullable(T)) query parameters not defaulting to NULL when omitted

[germiBest]

PR #93869 added support for omitted Nullable(T) query parameters defaulting to NULL, but used isNullable() which returns false for LowCardinality(Nullable(T)).
Changed to isNullableOrLowCardinalityNullable to cover both cases.

Closes #99805

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Omitted query parameters with LowCardinality(Nullable(T)) type now correctly default to NULL, same as Nullable(T).

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

[CLAassistant]

All committers have signed the CLA.

[clickhouse-gh]

Workflow [PR], commit [89161a9]

Summary: ✅

---

AI Review

Summary

This PR fixes omitted query parameters for LowCardinality(Nullable(T)) by replacing isNullable with isNullableOrLowCardinalityNullable in ReplaceQueryParameterVisitor::visitQueryParameter, and adds a focused stateless test. The change is small, targeted, and aligns behavior with existing Nullable(T) handling. I did not find correctness, safety, performance, or compatibility issues in the patch.

ClickHouse Rules

Item	Status	Notes
Deletion logging	➖
Serialization versioning	➖
Core-area scrutiny	✅
No test removal	✅
Experimental gate	➖
No magic constants	✅
Backward compatibility	✅
SettingsChangesHistory.cpp	➖
Safe rollout	✅
Compilation time	✅

Final Verdict

Status: ✅ Approve

[clickhouse-gh]

LLVM Coverage Report

Metric	Baseline	Current	Δ
Lines	83.80%	83.80%	+0.00%
Functions	24.00%	24.00%	+0.00%
Branches	76.30%	76.30%	+0.00%

PR changed lines: PR changed-lines coverage: 100.00% (5/5, 0 noise lines excluded)
Diff coverage report
Uncovered code