Enable Multiple Regex Paths in a VirtualServerRoute

[nginx-seanmoloney]

Problem: You cannot have Multiple Regex Paths in a VSR

A VSR can only contain one regex (or exact-match) subroute. You "must have only one subroute if regex match or exact match".​

Real World Example

• An API Gateway needs to route different API versions to different backends:

  /api/v1/* → legacy service
  /api/v2/* → current service
  /api/v3/* → beta service
  /api/internal/* → internal-only service

• Today, you must create 4 separate VSR objects, one for each regex pattern
• Or, add all of these routes to the VS, which makes the VSR obsolete for this use-case.

Result: Similar routing logic scattered across 4 VSR resources; harder to understand and maintain; more objects to manage

Acceptance Criteria:

• Controller should allow multiple subroutes in a single VirtualServerRoute
• Each subroute should support regex patterns and exact match patterns
• Ensure backwards compatibility, where existing VirtualServerRoute continue to work as expected
• Document the changes and create new examples in the repository