JQ dependency is too heavy for some setups

Depending on the jq library makes it difficult to install kcidb in restricted environments, particularly in AWS Lambda, which e.g. Tuxsuite uses.

Consider other options, e.g.:
* Replace jq with a custom pure-Python implementation. Shouldn't be too hard, as JSON specification is simple and well-defined, but might be rather slow on big datasets.
* Create separate tools with streaming support (e.g. `kcidb-submit-stream`, `kcidb-db-dump-stream`, `kcidb-db-load-stream`, and so on), and move them to a separate package, along with jq dependency.
* Use a library able to print out / parse JSON objects incrementally, and instead input/output complete JSON objects.

Start by auditing where the jq dependency is used across kcidb and how the named tools—kcidb-submit-stream, kcidb-db-dump-stream, and kcidb-db-load-stream—would be affected. Compare the proposed dependency, streaming, and packaging alternatives; done requires a decided approach that works in restricted environments while preserving the relevant tool behavior.

Written by the indexing model from the issue text.