ResourceUrlEncodingFilter cache misses are expensive

[dsyer]

A PetClinic user noticed this (https://github.com/spring-projects/spring-petclinic/issues/1732). For me it's a 2x throughput degradation on the home page of PetClinic, for the user that reported the issue it was 4x. The problem seems to be that ResourceUrlEncodingFilter has a CachingResourceResolver in it that works great for actual classpath resources. Conversely, links that are not static resources are cache misses, and they have to be checked every time in case they are, after all, on the classpath (e.g. links to other pages in the app).