Return exit code 0 when no features are found

Return exit code 0 when no features are found, or if no found features
match the tags filter used. Print the same message, that is used in the
currently thrown CucumberException when this occurs, as information
before the summary printout.
Add a dummy test case in JUnit report if no features are found

Jenkins will mark a job as failed even though the exit code was 0, if
the JUnit report file contains no testcase elements. Therefore add a
dummy testcase element to the JUnit report, when no features are found,
or no found features match the tags filter used.
Aviod passing null, improve message when missing feature path

Overload CucumberFeature.load to avoid passing null and the need for
null check. Improve the log message when no feature path is given at
the command line.
Created examples/java-no-features to demonstrate Cucumber JVM behaviour
when there are no features found at all.
Merge pull request #567 from brasmusson/succeed-on-no-features

Merge pull request #567 Return exit code 0 when no features are found,
or no found features match the tags filter. Update the History.md.