Default proxy config error management needs a review

The current proxy configuration is designed so that when un uncatght exception is thrown at some endpoint (response endpoint or request endpoint), then a generic error page is returned.

This page is intended to be read by a user but it not correct for http requests that starts from a wallet, such as an authorization response in direct_post mode. In those cases, we should **always** provide error responses compliant with openid4vp and the italian profile for openid4vp+sd-jwt