without this change we can't have a contract that will generate a stub but not a test. Of course that's for a reason since it's overriding the very essence of contract test.
with this change we assume that the users know what they're doing and that they will use this flag rarerly. Cause it means that you can have a false positive.
related to gh-881
* Add a switch to fail on no stubs
without this change we throw an exception if no stubs / contracts were found
with this change we catch exceptions from aether stub downloader and if there are no stubs found whatsover, and a switch is set to fail in that case, then we do throw an exception that no stubs / contracts were found
fixes gh-895
without this change we're not resetting default instances upon test finish
with this change we're resetting the default intance and setting it once more upon configuration startup
fixes gh-1081
* Generate stubs at runtime
without this change the producer side must publish the stubs for the consumer side to use them
with this change the consumer can toggle a switch so that the stubs get generated at runtime. This might of course lead to false positivies but we assume that the users know what they're doing
fixes gh-881
Currently Stub Runner can fetch a JAR, unpack it and only then pick the contract and stubs. Sometimes, what you want to achieve, is to point to a given folder where the stubs are already unpacked. Another option is a multimodule project, where the stubs are generated and then the user would like to just reference those instead of installing a JAR in a local m2.
With this change we suggest adding a protocol called stubs that would allow to define a path where the unpacked contracts and stub lay.
fixes gh-1150
