[LOGMGR-187] The ClassLoaderLogContextSelector should keep searching …

[jamezp]

…the call stack to find a log context.

In previous versions of the ClassLoaderLogContextSelector the entire call stack was searched. #160 introduced the JDKSpecific which short circuits when it finds the first matching class. That short circuits too early for this selector and it's the reason the CallerClassLoaderLogContextSelector was introduced.

This PR adds a new Collection<Class<?>> findCallingClasses(Set<ClassLoader> rejectClassLoaders) method to allow all valid callers to be returned.

[jamezp]

In cases where there is a registered LogContext this will slightly decrease performance. However in the experience of WildFly in most cases the entire call stack will be searched anyway. In most cases it would be suggested to use the CallerClassLoaderLogContextSelector. WildFly itself will switch to this new context selector.