"Failed to invoke" in lix run can be a bit annoying

[Gama11]

All that "failed to invoke" output makes it harder to spot what's actually important at a glance:

It's not correct either. It didn't fail to invoke, the command it invoked simply had a non-zero exit code.

[mikicho]

I think all the failed to invoke part is redundant and is suitable mainly to debug haxeshim itself, the failed command should print the error if necessary and haxeshim don't need to log it too.

@back2dos what do you think about to remove the failed to invoke part from the message?
src/haxeshim/Exec.hx

  static public function sync(cmd:String, cwd:String, args:Array<String>, ?env:Env)
    return switch spawnSync(cmd, args, { cwd: cwd, stdio: 'inherit', env: mergeEnv(env) } ) {
      case { error: null, status: code }:
        Success(code);
      case { error: e, status: code }:
        Failure(new Error(code)); // The message removed
    }