[PrefixPath GatewayFilter] does not honor URI template variables like [SetPath GatewayFilter] does #2438
Description
Is your feature request related to a problem? Please describe.
When it is not possible to use the SetPath GatewayFilter it would be great if the PrefixPath GatewayFilter could behave similarly about the URI template variables replacement.
I mean, if an incoming request matches a mapping rule thanks to the Path Predicate using a dynamic URI template variable (e.g.: /api/partners/{partner}/**) I would expect I can use that variable in almost every GatewayFilter but it seems a very few of them honor those captured variables, in particular SetPath GatewayFilter does while PrefixPath GatewayFilter doesn't.
Describe the solution you'd like
Add the URI template variable replacement also in the PrefixPath GatewayFilter, even better in all the other GatewayFilters where it has sense.
Describe alternatives you've considered
Actually I have been force to use the RewritePath GatewayFilter with the regex captured groups but it comes with a very high cost that I would avoid if possible.