Prepare Request Matching for Spring Framework Changes

[jzheaux]

In future versions of Spring Security, we should move away from PathMatcher (used by AntPathRequestMatcher) and HandlerMappingIntrospector (used by MvcRequestMatcher) as they are deprecated Spring Framework 7.0 M1.

This will also assist with efforts to simplify construction of path-based RequestMatchers.

• Add PathPatternRequestMatcher #16429

• Simplify Specifying servletPath in the Java DSL #16430

• Deprecate MvcRequestMatcher

• Deprecate AntPathRequestMatcher

• Deprecate usages of PathMatcher in Web Socket support

• Update HandlerMappingIntrospector Usage in CORS support

• Update HandlerMappingIntrospector Usage in Cache filter support

• Favor using PathPatternRequestMatcher in Java DSL
  We can default to Framework's PathPatternParser for MVC endpoints when HandlerMappingIntrospector#allHandlerMappingsUsePathPatternParser returns true

  We can default to Framework's PathPatternParser for non-MVC endpoints

  This should have an opt-in mechanism in order to remain passive.

[evgeniycheban]

Hi, @jzheaux, can I work on this? I'd want to start with adding PathPatternRequestMatcher along with tests.

[jzheaux]

Hi, @evgeniycheban, thanks for volunteering! Some of this is already addressed in a draft PR, so allow me to clean that up first so it's clear what work remains. I'll report back here when that's ready, and then we can divvy out the remaining work.