Align the step results in the JUnit test result files

Adjust the number of . separating the step text from the step result,
so that the results are aligned.
Add tests for the JUnitFormatter to disclose issues

The main issue is that the JUnitFormatter does not handle failures
in the before and after hooks properly. To add flexibility the tests
also specify that the JUnitFormatter should handle both all-steps-first
execution and one-step-at-the-time execution.
Fix issues in the JUnitFormatter

Change the JUnitFormatter to handle failures in the before and after
hooks properly. Also change the JUnitFormatter to handle both
all-steps-first execution and one-step-at-the-time execution.
Revert to all-steps-first scenario execution

To fix the missmatch between the PrettyFormatter from the Gherkin
library and Cucumber-JVM, by reverting the scenario execution to
all-steps-first execution as in Cucumber-JVM 1.1.2. This is possible
since the JSONFormatter in the Gherkin library in Gherkin 2.12.0
supports all-steps-first execution.
Upgrade dependencies
Revert version bounces
Merge pull request #556 from brasmusson/junit-formatter-fixes

Merge pull request #556 JUnitFormatter: Fix indentation, hook handling
and support all-steps-first execution.
Update the History.md
Merge pull request #557 from brasmusson/all-steps-first-execution

Merge pull request #557 Make the PrettyFormatter work by revering to
all-steps-first execution. This fixes #491 and the other reports of
IndexOutOfBoundsException when using the PrettyFormatter.
Update the History.md
Merge cucumber:master into brasmusson:pretty-formatter-test

Now when cucumber-jvm has reveted to all-steps-first execution, the
test case for the PrettyFormatter should pass.