Move log warnings about ignored ivy file content down to debug level. 

- Ideally, these should only be logged once when the module is actually resolved from a remote repository. 
- Once we don't use ivy.xml for internal meta-data persistence, we should be able to move these messages up to WARN, I think.
- Also, used the correct string substitution characters for log messages
Improved usefulness of log message: it was reporting default toString() representation
Recognise Marcin in release notes
Attach the tooling api caller's stack trace to the end of an exception constructed in the worker thread, so that the caller has some useful context about what they were doing.
Removed the cast for now, turns out not every model implements the protocol interfaces in every version.
Moved the adapting from protocol object to model object down closer to the provider, so that the adapting can be done based on the provider version.
GRADLE-2111: Fix ClassLevel category handling; add integtest coverage for include+exclude category setup
Pushed the mapping from model type -> protocol type and converting the resulting model right down to just above the provider.
Split ProviderConnection out of DefaultConnection, leaving the adapting to/from the consumer behind in DefaultConnection.
Changed CompatibleIntrospector so that it Just propagates the original exception when something goes wrong, rather than wrapping it.
Moved profiling integration test to core integ tests.
Added coverage for dependency resolution time in the profile report.
Added coverage for project evaluation time in the profile report.
Removed dead code from ProjectProfile
Profile report coverage and refactoring. Rename job for consistency.
Profile report coverage and refactoring. Added coverage for task status information.
Profile report coverage and refactoring. Added coverage for task duration.
Made the total configuration time in the "Summary" tab consistent with the value "All projects" in the "Configuration" tab. This way, the report no longer looks unsmart presenting different numbers for the same operation. The figures on the summary tab don't add up to the total build time and they never did AFAIR. I think this is a minor issue. Removed some no longer needed code in the BuildProfile.
REVIEW-1714 Refactored the logic behind sorting the items of the profile report and added coverage. We could push further and more improvements, like sorting alphabetically when elapsed time is the same, using tree sets to avoid redundant creation of collections. For now what's included in the commit should be enough.
Profile report refactoring - removed some code after finding common abstraction.