Log success if Ctrl-C in the middle of the execution

[bo-abstrlabs]

If it's not interrupted by Ctrl-C, the result is failing:

priceprover (main) priceprover submit
2022-04-29 11:12:41 INFO  CommandExecutor:53 - Submit price and proof to chain start
2022-04-29 11:12:42 ERROR CommandExecutor:30 - Submit price and proof to chain failed
2022-04-29 11:12:42 ERROR CommandExecutor:31 - Error ABLDR410: status_code=400,
2022-04-29 11:12:42 ERROR CommandExecutor:34 - TransactionPool.Remember: transaction 3FNHS6JCSJAV7MGKLSOVO7KTE7NZRKQJGEOS32GOY5BZRZBH5CSQ: logic eval error: err opcode executed. Details: pc=718, opcodes===
2022-04-29 11:12:42 ERROR CommandExecutor:34 - bnz label8
2022-04-29 11:12:42 ERROR CommandExecutor:34 - err
2022-04-29 11:12:42 ERROR CommandExecutor:34 - label8:
2022-04-29 11:12:42 ERROR CommandExecutor:34 - 
2022-04-29 11:12:42 ERROR CommandExecutor:34 - context={"scriptPath":"scripts/call-verify.js"}
2022-04-29 11:12:42 ERROR CommandExecutor:34 - For more info run algob with --show-stack-traces or add --help to display task-specific help.

But it's logging as success when Ctrl-C immediately:

priceprover (main) priceprover submit
2022-04-29 11:12:24 INFO  CommandExecutor:53 - Submit price and proof to chain start
^C2022-04-29 11:12:25 INFO  CommandExecutor:38 - Submit price and proof to chain successfully
2022-04-29 11:12:25 INFO  TransactionSubmitter:40 - Proof validated by zkp_verifier. Submit success

Exit code in this case was 130, which is correct, so just the logging issue. Maybe the same issue as #2

[Ryuya1995]

Add an validation mechanism for input/output files for command execution:
d520eef

The actual fix will be made by update all command.excute to include this validation