Multiple path matches for routes #2987
Description
What should we add or change to make your life better?
Looking at the "all config properties", it looks like certain match filters can be provided with multiple values. I know some must support disjunction (a request can't have multiple hosts or methods, so it must match at least one of the provided values) and others might support conjunction (all of these header or query parameter filters must match), so why can't the Path section be an array of accepted path patterns? In order to do this now, you have to create 1 route for every path, when you could only need 1 route with multiple paths and 1 cluster.
Why is this important to you?
I'm working on a reverse proxy for my teams to use when developing web services locally. Most requests will go to a service with a one-to-one relationship with a cluster (e.g., exactly one route matches exactly one cluster). However, some requests might go to services that are run in a monolithic server (e.g., multiple services, each with their own route, run on the same host). It would be nice to have one cluster and one route for all of the different paths that should go to that one server.
I saw #1318, but I'm asking for the ability for a single route config to support multiple paths.