Fix JSON parser to allow control characters in JSON string input

[PHILO-HE]

JSON string input can contain control characters, e.g., new line character \n. It can be
correctly handled by Presto, but not allowed by simdjson lib. If it exists in input, simdjson
will return UNESCAPED_CHARS error, then Velox will output null. Simdjson only allows literal
\n (represented by \\n). See its code link.

Here is a test result with presto.

SELECT json_extract('{"c1":"ab\ncd"}', '$.c1');
  _col0
----------
 "ab\ncd"
(1 row)

Just created one discussion thread in simdjson community: simdjson/simdjson#2287.

[netlify]

✅ Deploy Preview for meta-velox canceled.

Name	Link
🔨 Latest commit	960f35d
🔍 Latest deploy log	https://app.netlify.com/sites/meta-velox/deploys/6729afcfa84e260008816259

[kgpai]

Hi @PHILO-HE , I am working on canonicalization of jsons (#11284); Ideally we aim to handle escaping during canonicalization (i.e from json_parse or when say cast(x to json)).
Looking into the example you raised, I am wondering if this is another way we should handle canonicalization (cc: @gggrace14 )