Automaticlly adding version to route breaks some routing configurations

[carnage]

Bug Report

Q	A
Version(s)	latest/all

Summary

When an API is set to use url versioning, the listener auto prepends the version segment into the route config however, it doesn't check the route TYPE. If the route type is anything other than Segment, it will break the routing and mean the route will never match.

How to reproduce

1. Enable url versioning on a route.
2. Set it's route type to Literal

Expected behavior

Suggest either automatically changing the route type to Segment or throwing an exception stating that the route must already be a segment route type.

[weierophinney]

Transferred this to the api-tools-admin repo, as this sort of check needs to happen during an admin operation.

Alternately, or potentially in addition to, we can add some functionality to api-tools-versioning to raise an exception when it encounters a non-Segment route.

[carnage]

The admin tool doesn't create routes which don't work; this happens if configuring manually and would also be an issue if you used the module as a stand alone so it definitely needs to raise an exception in the api-tools-versioning component.