v0.11.0: Stop Quke from returning 0 exit status despite passing tests (#112)

https://eaflood.atlassian.net/browse/RUBY-1373

The default behaviour here is for Cucumber to exit as soon as a single test fails. We prefer to run the full suite each time, so these errors were being rescued.

However, this meant that if a test did fail, the exit status of the job would still be 0, which isn't what we want for our CI.

This PR changes the behaviour of Quke to record if a test fails, allow the test suite to proceed, and then throw the error at the end instead.

Cucumber will also call a SystemExit when the suite has finished running, or if there is some other problem with the suite. We don't want to consider the successful runs as errors or the suite will be considered "failed" every single time.

Version 0.2.1

Version of Quke now as a gem, though still to be tested fully in this context.

Original template version

This release marks the last point Quke got to when in the form of a template project, rather than a gem to be used in your own project.