Add a new NDJSON / JSONL input source

[bradlarsen]

This adds a new input source to TruffleHog, accessible via trufflehog json-enumerator.

This input source requires a list of filenames, each of which is an NDJSON-formatted sequence of objects that take one of two forms:

Form 1: {"data": "utf-8 string", "metadata": <non-null JSON value>}
Form 2: {"data_b64": "base64-encoded bytestring", "metadata": <non-null JSON value>}

The data / data_b64 field specifies the content to be scanned. The metadata field is arbitrary, and is simply propagated downstream with scan results from the corresponding content.

Note that although trufflehog json-enumerator requires a list of filenames to be given, the NDJSON data that you wish to scan may not need to be first written to disk. On Linux and macOS, at least, you can use shell process substitution to set up a named pipe from a producer process, like trufflehog json-enumerator <(some-program-that-emits-ndjson).

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[rosecodym]

This looks like a good start! In addition to my inline questions, I have this one: Are scans of individual paths cancellation-aware? It looks like the source is only cancellation-aware between paths.