Improve exception handling in general

As indicated in the discussion regarding #2416 the exception handling in DependencyCheck should be further analyzed in order to create a more structural fix for the issue that with multiple exceptions during analysis the resulting message and stacktraces provide a clear view on the issue(s) at hand.

In that evaluation among others we should make sure that the (immutable by convention) characteristics of Exceptions (they should provide a read-only view of the application state at the time the exception was raised, mutators are intended to be used only while constructing the exception) is honored.

Solutions/alternatives to be considered will follow later.