Align AbstractFilterRegistrationBean dispatcher types with servlet spec

[philwebb]

The default dispatcher types defined in AbstractFilterRegistrationBean were originally copied from AbstractDispatcherServletInitializer.getDispatcherTypes() however they continue to cause problems.

Rather than trying to pick our own set we should align with the servlet spec and use DispatcherType.REQUEST as the default.

We will then need to check our own configuration of filters to see if specified dispatcher types are required for them.

[cemo]

It would be cool to be set default values from configuration files.

[wilkinsona]

This change will mean that FORWARD, INCLUDE, and ASYNC are removed from the default dispatcher types. The loss of FORWARD and INCLUDE appears to be inconsequential. The loss of ASYNC does have an effect: it means that the security context is now null within an async dispatch. I think we should change the default there.

[cemo]

@wilkinsona see #4505 (comment) please. I still believe that ERROR, ASYNC and REQUEST are suitable for default. These 3 dispatcher type are usually the beginning of request chains. However FORWARD and INCLUDE are not used at the beginning of request, instead they are used after.

[wilkinsona]

Sorry, @cemo, but we're not going to change our decision to use REQUEST as the general purpose default as we want to align with the Servlet spec. Just to be clear, my comment above was specifically with regards to the default for the security filter.

[cemo]

Thanks @wilkinsona, really makes sense to align with spec.

[wilkinsona]

See #8288 and #8289 for exceptions to the new default of REQUEST.