Unclear "wrong output format" when Sanger alignment fails

This issue blocks UGENE-7901, because it is very easy to reproduce the problem of this issue using the scenario from UGENE-7901.

The scenario from UGENE-7901 has an error "wrong output format" in Sanger alignment, which has been run with dialog. This error sign is as much unclear as possible, and users have no clue about what happened and why their alignment failed.

I have been investigating this problem for a little bit, and found out its approximate reason. As you may know, when you run Sanger alignment with the dialog, it runs in the child process. The communication between parent and child processes is a bit complicated. If we are talking about our case, we use an intermediate file. The child process (the one which makes Sanger alignment calculations) saves the status of the execution to this file, and the parent process (the main UGENE process with GUI) reads this file after the child process has been finished its executing. But, if child process failed to run calculations correctly (as it has happened in UGENE-7901), it turns out, that the calculation file is empty and the parent GUI process just has no idea about the child process calculations. In this case, it writes the short message "wrong output format" and that's it.

It happens because the child process faced some problems in `onSubtaskFinished()` function (the exact point for the above mentioned scenario is here), which is still preparing stage, but writing to the output file appears to be here (which is already run stage). Shortly to say, the problem appears very early and task stops its executing.

What should be done:

1. First of all, you need to add a parameter, which makes child CMD process writes its log to file. This file should be located in the "UGENE data directory".
2. The second thing - if the process finished its calculations correctly (without errors), then the file from the previous point should be removed. But, if some errors appeared, then in the task report (in the main GUI process) you should write something like this:

   The child process has execution errors, please, investigate the log file: the/log/file/link.txt
   

   The same message you should have in the log on the "error" level.

1. Get the main error of WorkflowRunFromCMDLineBase and add it to report.
2. Remove "wrong output format" sign, it should not apeear anymore.