fixing some compiler warnings in inline tag handler
using a mock watch service for most file modification service tests
removing 'FileModificationWatcherThread.start() in a test that was accidentally added
updating all file versions if we get an OVERFLOW event from the java watch service
making sure we cancel and remove references to any invalid watch keys
logging a warning if a watch key could not be reset but the path still exists
Merge branch 'develop' into file-change-watcher-refinements
fixing how/when the watch key reset warning is logged
test path is displayed when running tests from command line
Merge pull request #1073 from BladeRunnerJS/develop

v0.14 release
unified getTestPath method
Merge branch 'master' into file-change-watcher-refinements
Merge branch 'mocks-for-file-modification-thread-test' into file-change-watcher-refinements

Conflicts:
	brjs-core/src/main/java/org/bladerunnerjs/memoization/FileModificationWatcherThread.java
	brjs-core/src/main/java/org/bladerunnerjs/plugin/plugins/bundlers/inline/InlineTagHandlerPlugin.java
changing 'watch key could not be reset' log level to debug
incrementing all file versions if there is an OVERFLOW event on the watch service
increasing the watch service sensitivity if the neccessary class is available
making watch service an interface so we can have 2 implementations
creating a WatchService factory
adding the extra WatchServices that are used if the relevant classes are available
adding an extra test and removing the OS specific checks in WatchServices since it only depends on whether the class/field is available