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
why is this a valid reason for failure, but lots of other non-zero exitcodes from `CAF::Process` not? (to be honest, i don't know what other exitcodes except command failures `CAF::Process` can have)