Improve EvoCrash demo documentation

Issue Type: test report
Reproducibility: always
Severity: feature
Tool/Service/Component: EvoCrash Demo, latest version
Execution Environment: Linux Tumbleweed
Reporter: Jesús Gorroñogoitia <a rel="noreferrer nofollow" target="_blank" href="mailto:jesus.gorronogoitia@atos.net">jesus.gorronogoitia@atos.net

EvoCrash demo documentation needs some improvements:

It is not clear if potential users (i.e. use case evaluators, for instance) should start from the EvoCrash instance contained within this demo or if on the contrary the latest release from the EvoCrash repository should be obtained, built and used instead.
This documentation can constitute a getting started document, but I am missing a reference to a EvoCrash user guide that provides information to configure and use the tool for any codebase and crash replication scenario.
Documentation does not describe the location of Evocrash output files: -- search process report in csv, located at ./evosuite-report/statistics.csv -- generated test cases, located at ./src/GGA-tests/java
The documentation is confusing in the order of required activities. It request to runt the generated test and later on, it requests to edit the tests, but this edition should be done before running the tests
The instructions to edit the generated tests, preventing the execution errors reported in bugs is confusing. The try-catch block should be removed but NOT the code lines within the try block itself. That is, the two lines of code within the try block should be kept.
Although test are requested to be executed with Gradle, documentation shows the test execution logs shown within an IDE or similar test execution engine, since Gradle does not show these logs. It informs one test failed. Test logs can be inspect by opening the report in a browser.

STAMP-project / EvoCrash-demo