Find code coverage/profiling tool (for bash/jq)

[chrismre]

Looking at where we're missing on the coveralls, they seem pretty easy... it's a lot of malformed input stuff, etc.) We should make sure we handle failures gracefully... I know everyone is busy, but it highlights for us a bunch of easy to fix tests.

To be concrete, it looks like we can get into the high 80s or low 90s with a code cleanup pass.

@SenWu is probably in charge of some of this? and I would also guess @netj oversees it?

[netj]

Increasing test coverage will happen in the next release.

[chrismre]

:(

[netj]

Due to the lack of code coverage tools for our primary languages: bash and jq, code coverage and coveralls badge has been dropped. I'd say we should do a more thorough code review of these less bloated code. Nobody would argue that one should write database queries in C just because their coverage can be easily measured while it's not so for SQL. Anyway, having a simple profiling tool that shows which commands are actually unused or used how many times may be useful, though. Let's keep our eyes open looking for such tool and track it in this issue.