Fix API Version with Status Using URL Segment Method

[commonsensesoftware]

Fix API Version with Status Using URL Segment Method

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

Fix extracting API version with status using URL segment method. This is a limitation of how constraints are matched and parsed in route templates. This will add ever-so-slightly more overhead to matching API versions on incoming requests when versioning by URL segment, which was already the slowest method.

A nice side effect is that this same fallback mechanism works for matching incoming API versions for gRPC endpoints that version by URL segment because gRPC endpoints have their own route templates that do not map to constraints. This would make it near impossible to match such endpoints. gRPC endpoints can also version by query string, which does not have this issue nor any of the performance impact.

• Fix API version with status property returns 404 when called #1187
• Support versioned gRPC endpoints by URL segment method Issue when using AddApiExplorer and JsonTranscoding #1109