DependencyBundleResolver now uses matcher strategies
- DependencyBundleResolver now uses matcher strategies to find whether a
class name matches a class file
- added ClassName class that tries to encapsulate a validated fully
qualified class name
- added ClassFile class that tries to encapsulate a validate .class file
present on the file system or in the classpath
- added StringDepenencyMatcherStrategy that checks a short class name
vs a filename without the extention to find whether a class name matches
a file
- added much needed sarcastic comments
- added pointless slow validations all over the place
- added tests for all of the above (tests barely cover 10% of the code
but still ...)