Fix NULL parameters in Tuples/Maps/Arrays

[slvrtrn]

Summary

Resolves #374
There was a similar issue with Array/Map types, too - JS null and undefined should be printed as the NULL keyword instead of \N there, as \N can be used only for non-nested types, e.g. for something like Nullable(Int32).

See

curl "http://localhost:8123?param_tup=%5B'foo',NULL%5D" --data-binary "SELECT {tup: Array(Nullable(String))} t" 
['foo',NULL]

curl "http://localhost:8123?param_tup=%5B'foo',\N%5D" --data-binary "SELECT {tup: Array(Nullable(String))} t"
Code: 26. DB::Exception: Cannot parse quoted string: expected opening quote ''', got '\': value ['foo',\N] cannot be parsed as Array(Nullable(String)) for query parameter 'tup'. (CANNOT_PARSE_QUOTED_STRING) (version 24.12.2.29 (official build))

But

curl "http://localhost:8123?param_tup=\N" --data-binary "SELECT {tup: Nullable(String)} t"  
\N

Checklist

• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG

[slvrtrn]

The tests should be green when we update the JWT credentials.