Fix for Content negotiation should fallback to the first formatter that can write the type #1033

let's say a user's application has json and xml input formatters...now if a client of this user's application is sending an accept header with media type like `application/foo`, then how do we expect to the use the `StopIfNoMatchOutputFormatter`...

The thing is if user's application has to send back `406` status code all across the application(because a client of this application could be asking for `application/foo` to any endpoint), he might wish to do it in one central place, in which case adding `StopIfNoMatchOutputFormatter` to global formatters is an issue...