PathPatternRequestMatcher is not a suitable replacement for the deprecated MvcRequestMatcher

Describe the bug
Due to the deprecation of MvcRequestMatcher, its replacement 'PathPatternRequestMatcher' requires to know the servlet path(s) beforehand. In my usecase i cannot know this.

To Reproduce

1. Have the security chain defined in a seperate autoconfigure module. With a permitAll path.
2. Have a servlet path defined in the application that uses the autoconfigure module.
3. In the old (mvcrequestmatcher) situation: request /servlet-path/permit-all-path = 200
4. In the new (pathpatternrequestmatcher) situation: request /servlet-path/permit-all-path = Err

Expected behavior
Another matcher that can dynamically add the requestMatchers to each registered servlet within the applcation, without requiring me to know the servlet paths beforehand.

Sample

See a sample in this repo: https://github.com/genie137/demo-depr-webmvc-matcher
I have taken the important parts from closed source libraries to reproduce.