clp-s: Report exactly where parsing error occurs when parsing JSON (fixes #514).

[gibber9809]

Description

This PR adds reporting for where a parsing error occurs within a JSON file, and fixes an issue where parsing exceptions were sometimes not caught.

We add some code to the main parsing loop to keep track of how many bytes from the current file have been consumed up to the previous record. When an error occurs we are then able to report how many bytes were parsed successfully .

We also wrap the main "parse_line" function in a try/catch block. Even after getting a valid iterator to a record it seems that certain kinds of invalid fields can throw latent errors in simdjson, which previously went uncaught. Instead of trying to add error handling for every single time we access a field within parse_line we just catch the thrown errors.

Validation performed

• Validated that we correctly report 0 bytes parsed when the first record is invalid
• Validated that we report an accurate offset to the invalid record when we have malformed JSON several MB into a file
• Validated that exceptions are caught and logged correctly for a variety of invalid JSON log files

[wraymo]

The PR titles is good to me.