Refactor AbstractRestResponder and Responder interface interact better with CDI

Currently, subclasses of AbstractRestResponder are required to call it sole constructor which takes a MediaType as a parameter. But this will cause issues with CDI if for example a user would like to use a different scope for a custom responder, as CDI requires a no-args constructor for various operations (like creating a proxy).

This task should remove the constructor from AbstractRestResponder and let subclasses manages this them selves.

This tasks should also add a deployment time check to verify that a Responder implementation provides a no-args constructor. If not provided the will be no way for the user to notice that their custom responder was not picked up, they would only notice that it is not working.