runcmd: Fix quoting issues when running commands

The important part of this patch is one line that makes sure that if
we're in single quoted mode, we should ignore '\' as an escape
character.

Without this, foo\\bar was interprented exactly the same as 'foo\\bar'.
With it, the former is executed as one backslash, the latter as two.

There's is also a new test-runcmd, with a small set of test cases for
the command quoter.

Signed-off-by: Robin Sonefors <robin.sonefors@op5.com>
checks: Check command output does not show up pre-escaped

Why would you think it did?

Since we assumed that check output was escaped, we tried to unescape
it, and that becomes highly weird.

So, this bug meant that, unless a command is quoted (which, as shown in
the parent commit, you couldn't do), if you're trying to test quoting by
writing a check command that echoes your input, you needed four
backslashes in your input to get one in your output. Trying to read the
quad-escaped commands in the input, in turn, quickly makes a user want
to escape from this application.

Signed-off-by: Robin Sonefors <robin.sonefors@op5.com>
base/nebmods: Log module loading errors to stdout

It's really, really tiresome to watch logs for module errors
when Nagios just keeps rolling on in case it can't load one or
more modules. This patch makes sure at least errors are printed
to stdout as well.

Signed-off-by: Andreas Ericsson <ae@op5.se>