Fix exception in intDiv/intDivOrZero on arrays of nullable tuples

[Algunenano]

executeArrayWithNumericImpl in FunctionBinaryArithmetic passed the input array's element type as result_type to the inner executeImpl, instead of the result array's element type.

This was harmless when actual values existed (the tuple function ignores result_type and computes correct columns via elem_func->getResultType). But when all elements are NULL, IFunction::execute's default Nullable handling short-circuits and creates a default column using the passed result_type:

if (rows_without_nulls == 0)
    return result_type->createColumnConstWithDefaultValue(...)

With the wrong result_type (e.g. Nullable(Tuple(Float64, Float64)) instead of Nullable(Tuple(Int64, Int64))), this produced Float64 columns while serialization expected Int64.

Closes #100873

Changelog category (leave one):

• Critical Bug Fix (crash, data loss, RBAC)

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

Fix exception in intDiv/intDivOrZero on arrays of nullable tuples, e.g. SELECT intDiv([divide((1, 2), ... AND NULL)], 2).

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

[clickhouse-gh]

Workflow [PR], commit [93ad667]

Summary: ❌

job_name	test_name	status	info	comment
Upgrade check (amd_release)		failure
	Changed MergeTree settings are not reflected in the settings changes history (see changed_merge_tree_settings.txt)	FAIL	cidb	IGNORED
	New MergeTree settings are not reflected in settings changes history (see new_merge_tree_settings.txt)	FAIL	cidb	IGNORED

---

AI Review

Summary

This PR fixes a real type mismatch in executeArrayWithNumericImpl by passing the nested return element type to executeImpl for array/number operations, and adds a focused stateless regression test covering both NULL-only and non-NULL paths. I did not find correctness, safety, concurrency, or performance problems 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	➖
PR metadata quality	✅
Safe rollout	✅
Compilation time	✅

Final Verdict

• Status: ✅ Approve

[clickhouse-gh]

LLVM Coverage Report

Metric	Baseline	Current	Δ
Lines	84.10%	84.10%	+0.00%
Functions	24.50%	24.60%	+0.10%
Branches	76.70%	76.70%	+0.00%

Changed lines: 100.00% (5/5) · Uncovered code

Full report · Diff report