Bug: Premature EOF in JSON leads to status 500 instead of REQBODY_ERROR

Describe the bug

Instead of failing safely, ModSec triggers a status 500.

$ cat example.json
{ "id" : "123"
$ curl -v http://localhost -H "Content-Type: application/json" -d @example.json
...
< HTTP/1.1 500 Internal Server Error
...

Logs and dumps

[2022-10-05 11:17:58.926606] [-:error] 127.0.0.1:39976 Yz1Lxuf_TBfAeTSTcu5oFwAAAAk [client 127.0.0.1] ModSecurity: JSON parser error: parse error: premature EOF\n [hostname "localhost"] [uri "/"] [unique_id "Yz1Lxuf_TBfAeTSTcu5oFwAAAAk"]
[2022-10-05 11:17:58.926624] [-:error] 127.0.0.1:39976 Yz1Lxuf_TBfAeTSTcu5oFwAAAAk [client 127.0.0.1] ModSecurity: JSON parser error: parse error: premature EOF\n [hostname "localhost"] [uri "/"] [unique_id "Yz1Lxuf_TBfAeTSTcu5oFwAAAAk"]
[2022-10-05 11:17:58.926629] [core:trace3] 127.0.0.1:39976 Yz1Lxuf_TBfAeTSTcu5oFwAAAAk fixups hook gave 500: /

Server (please complete the following information):

• ModSecurity version (and connector): ModSec 2.9.6
• WebServer: Apache 2.5.54

Additional information:

I played around with broken JSON payloads following a customer request. This was the only case where I could make ModSecurity stumble.

No source file, test, or entry point is named. First reproduce the malformed JSON request against ModSecurity 2.9.6 with Apache, then trace handling of the reported JSON parser error; done means the premature EOF fails safely with REQBODY_ERROR instead of HTTP 500.