Undaemonize Cisco run_csd_script

#108 (closed) is a good example of the confusion that the current behavior causes:

• Main process spawns grandchild daemon process to run CSD script/binary, continues running
• Grandchild process fails in some way. It prints to the log, but can't return its exit status to grandparent
• Main process spins forever on the “wait page”

This MR makes the Cisco run_csd_script work like the GP run_hip_script: it runs the Trojan/scanner process as child, waits for it to finish, and reacts to its exit status.