[AS7-5422] Fix logging DUP to be more deterministic in it's scanning behavior

[AS7-5422] Only search META-INF and WEB-INF/classes directories for logging configuration files. Also only check the top-level and sub-deployments, but other deployment dependencies.

The log context selection is based on the deployments class loader. The DUP first checks the top-level deployment for a logging configuration. If a logging configuration file is found a new log context is created and the top-level deployment and any sub-deployments that do **NOT** have their own logging configuration are assigned the new log context.

If a sub-deployment contains it's own logging configuration file, then a new log context is created and sub-deployment is assigned the new log context.

If no logging configurations are found, the DUP then looks for a ```Logging-Profile``` ```MANIFEST.MF``` entry on the top-level deployment, then each sub-deployment. The sub-deployment processing works the same as the per-deployment logging.

The DUP no longer looks recursively in each dependency for a logging configuration. This is different behavior than what is EAP 6, but it is more what the behavior should have been.