Failed enrichers cause exception to be thrown as response

Currently when any of the enrichers fails the exception is thrown as response thus preventing access to anything else (body, other enrichers, etc..).

Regardless of enricher failures the request itself should not fail, so, as a first step, we will simply:

• catch any enricher error
• not include the failed enrichers in the answer (=> no contexParameters entry for that enricher)

This would allow clients to have access to the response while still being able to know which (if any) enricher failed (with logs visible on the server, no client side error reporting on enrichers for now).