Semicolons removed in multi-query requests to `/cli_json`

[Nick-S-2018]

Bug Description:

If you make a multi-query request with a fuzzy search query to the /cli_json endpoint , daemon replaces the semicolon in it with the \u0000 character before routing the request to Buddy.

curl localhost:9308/cli_json -d "CREATE TABLE t(f text) min_infix_len='2'"
[{"total":0,"error":"","warning":""}]

curl localhost:9308/cli_json -d "INSERT INTO t(f) values('abcdef')"
[{"total":1,"error":"","warning":""}]

curl localhost:9308/cli_json -d "SELECT f from t where match('abczef') option fuzzy=1; show meta";
{"error":"P01: syntax error, unexpected $end near 'option  '"}

It can be seen in Buddy log that the request coming to Buddy is changed in comparison with the initial one, so Buddy fails to handle it:

request data: {"type":"unknown json request","error":{"message":"unknown option 'fuzzy'","body":{"error":"unknown option 'fuzzy'"}},"version":3,"message":{"path_query":"/cli_json","body":"SELECT f from t where match('abczef') option fuzzy=1\u0000 show meta","http_method":"POST"}}

Manticore Search Version:

Manticore 13.13.4 0bc5a9641@25101507 dev

Operating System Version:

Ubuntu 22.04

Have you tried the latest development version?

Yes

Internal Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

Details

• Implementation completed
• Tests developed
• Documentation updated
• Documentation reviewed

[Nick-S-2018]

Blocks manticoresoftware/manticoresearch-buddy#507

[github-actions]

Thanks for the update! However, the internal checklist is not yet complete. A Manticore team member will close this issue once everything is checked off. 🛠️

[tomatolog]

the issue was fixed at 0433fe3 and the fix is similar to already done 4564fe4

As the SQL parser put and move the null terminator during the parse of the statement but if it failed it keep that terminator at the source statement that is why I use the fix that was already done for /sql endpoint

If the issue fixed completely for Buddy it could be better to add CLT tests similar to tests added for #2603

[Nick-S-2018]

Yes, it works as expected so we can add CLT tests now.
@PavelShilin89 pls, add them based on the requests from the issue description.