Fix Assuming Default Version with Version-Neutral

[commonsensesoftware]

Fix Assuming Default Version with Version-Neutral

• 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

If an API defines multiple endpoints where one can be matched implicitly using the default API version and another is version-neutral, the version-neutral API is given precedence. The endpoint for the default API version is not version-neutral so it does not match. Simply changing the precedence also does not work because there is no version-neutral destination in the assumed, default version destination. This changes the precedence and adds a version-neutral destination, if any, to the assumed version destination when present. This allows both sets to be routed together.

• Fixes AssumeDefaultVersionWhenUnspecified does not work correctly if ApiVersionNeutral is used in the controller #1083