Macros: Make each macro tell which escaping capabilities it accepts

Not all macros should appearently accept command line escaping, but
just a few related to plugin output, and user input.

This commit builds that table again, which was available earlier in
another form. But this time, it isn't used to tell how to escape a
macro, but just which kinds of escaping that should be possible.

While at it, rearrange the macro_key_code struct somewhat to avoid
fill-spill on 64-bit architectures (AE).

Signed-off-by: Andreas Ericsson <ae@op5.se>
Signed-off-by: Max Sikström <msikstrom@op5.com>
Macro tests: Make test for macro generation match updates in macro code

Earlier macro code broke conisitancy with the documentation. Previous commit
fixed that inconsitancy, so lets patch the tests to match

Signed-off-by: Max Sikström <msikstrom@op5.com>
lib/worker: Forward status of SIGCHLD-reaped events to scheduler

Without this patch, all checks reaped via the reap_jobs() function
would otherwise appear to be 100% ok, consume no resources and take
no time at all to execute. Like inventing quantum computing, except
not really...

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