Fix ncm-cdispd forgetting about failed configuration modules

- Fix function used to run ncm-ncd not returning ncm-ncd status
- Use `CAF::Process` to execute ncm-ncd
- Properly retrieve ncm-ncd status (fix for the buggy value that has
always been returned)
- Improve debug logging

Fixes #4
if `CAF::Process` would check the existence of the executable, it would exit with an exitcode > 0 but < 256, right? but the code above (`$result = $? >> 8`) would still consider it a success.
my point is: what other non-executable related scenarios should be considered a failure (or maybe better: why aren't all exitcodes relevant?)