bug(api): NaN/Inf render as null on /v1/query but as "nan"/"inf" strings on the stream

[EricAndrechek]

Found while documenting the type layer in draft PR #712 (branch chtypes-v2).

Problem. Float NaN and +-Inf render as null on /v1/query and pipes, and as the strings "nan", "inf", "-inf" on the stream. A live query can mix the two. Measured on a ClickHouse 26.8 build: the chtypes export ignored output_format_json_quote_denormals whether it was 0, 1 or unset, and returned no unsupported-setting error.

The server also accepts "nan"/"inf" strings on insert (stored as nan/inf), while null stores 0 or NULL (measured), so pinning the setting alone would not make the surfaces round-trip.

Related: #365 (pipes NaN/Inf serialisation).

Waiting on: chtypes honouring the setting in its export (tracked upstream in chtypes). Today documented as-is in sdk/reference.md and api.md, with a test pinning the stream spelling.

[EricAndrechek]

Update from #712 on chtypes 1.0: chtypes' export now honours output_format_json_quote_denormals. At the default (0) it would export NaN/±Inf as null, and the worker's insert would then store 0 in a non-Nullable float column (measured).

So the ingest path now pins output_format_json_quote_denormals=1. Ingest and the stream keep the strings "nan"/"inf"/"-inf", and storage keeps the float values. An integration test asserts both.

/v1/query and pipes still render null (quote_denormals=0 on the read path), so the mismatch this issue describes is unchanged.