Bugfix release: Run MatchProcessors in the calling thread for synchronous scans, to avoid a possible class initialization deadlock.
(Previous to this release, it was possible to enter a state of classical class initializer deadlock if FastClasspathScanner was called asynchronously from within a class initializer block, and a user-provided MatchProcessor tried to access a field or method of the same class, since the MatchProcessors were run on a separate thread -- bug #103.)