Create "explain plan" for when a request does not match #7
Description
Currently when a request does not hit your resource method, one is often forced to debug the following classes:
BaseHandler -> BindingMatcher -> MatchQuality -> ParameterExtractor
Also the app currently vomits Yadic exceptions when in debug mode in a vain attempt to help you work out what went wrong. This tends to actually be a red herring for most users.
Lastly it's quite easy to write a resource binding that contains a typo (say in a PathParam) which will mean the resource will never match.
To resolve all these issues I suggest we create an explain mode (much like the profile mode) that shows you why every resource did not match.