SocketExceptions are no longer handled as error

This commit introduced a special handling for SocketExceptions under the assumptions that the only Socket Exceptions can happen when Sling/Jetty fails to stream back the response to the client (browser).

But there are other types of SocketExceptions, which can happen during page rendering, e.g. when a Servlet/Script does connections on its own, for example to fetch data from a backend system. If these exceptions are wrapped and thrown, it could lead to a situation, that the error handling in this place is actually not kicking in at all, and also no logging for this exception is done at all.