Restructure AuthenticationServiceException handling

An AuthenticationServiceException represents something that went wrong on the server side. As such, it shouldn't be handled by AuthenticationEntryPoints.

This means that likely is shouldn't be handled by ExceptionTranslationFilter or any of the authentication filters.

However, because this class extends AuthenticationException, it is required for each component to somehow opt-out of handing to its AuthenticationEntryPoint.

One way to address this is to change AuthenticationServiceException to no longer inherit from AuthenticationException. Another way would be to add a new exception like AuthenticationServerErrorException -- similar to spring-web's HttpServerErrorException -- that doesn't inherit from AuthenticationException.

Start by tracing how AuthenticationServiceException is handled by ExceptionTranslationFilter and the authentication filters, especially where they route AuthenticationException instances to AuthenticationEntryPoint implementations. Compare changing its inheritance with introducing an AuthenticationServerErrorException modeled on spring-web's HttpServerErrorException. Done means server-side failures are no longer routed to authentication entry points without leaving affected components inconsistent.