Using versioning in conjunction with yarp reverse proxy

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

We have a legacy .net framework and configured YARP to do a reverse proxy between the legacy one and the .net 6 migration one.

Those are working smoothly together but when I added a versioning library to implement API versioning inside .net 6 project for future developments, the reverse proxy didn't work anymore for the legacy API URLs.

Dotnet frameworks working under /v2 version and .net 6 would work in /v3 and uppers, but requests won't be redirected to /v2 anymore as APIVersioning assumes it as an invalid version.

I was looking for a way to override APIversioning middleware in some way but it seems it's not possible.

### Describe the solution you'd like

I think its really needed to have a way to override middleware or something else to implement such scenarios

### Additional context

_No response_