Add fireTestStarted/Finished for undefined/pending steps in strict mode

The JUnitReporter should for each call to Result either call
fireTestIgnored, or call fireTestStarted and fireTestFinished on the
step notifier. In strict mode undefined and pending steps should be
treated as failed steps, so fireTestStarted and fireTestFinished should
be called on the step notifier.
Correct JUnit notification for background steps

The background steps are copied in the ExecutionUnitRunner for each
scenario in a feature with background. This is done to make them unique
for each scenario, so that the JUnit notification later will not be
ambiguous. When the background steps are executed, it is the original
ones that are executed. Therefore the background steps need to be
'converted' from the original steps to the copies made earlier, when
performing the actual JUnit notifications for an execution unit
(scenario).
Merge branch 'junit-notify-on-background-steps' of https://github.com/brasmusson/cucumber-jvm into brasmusson-junit-notify-on-background-steps
Fix compilation problem. Closes #659, #660
Merge branch 'brasmusson-junit-notify-on-background-steps'
Merge branch 'junit-reporter-fire-on-step-notifier-for-every-step' of https://github.com/brasmusson/cucumber-jvm
Attribution for #656
Bump dependencies
Prepare for 1.1.8 release
[maven-release-plugin] prepare release v1.1.8
[maven-release-plugin] prepare for next development iteration
merge pom.xml