Enhance resolver logging to get better uses diagnostics

There is lots of useful information the resolver encounters while trying to resolve a consistent class space having to do with uses constraint violations. The felix resolver encodes a nice chain message contained in a ResolutionException that can help diagnose uses constraint issues.

It would be helpful if the Logger was enhanced to be able to capture the ResolutionException for uses constraint violations as they occur during the resolve process.