Using RouteConfig version defaults in Controller selection

I found this useful for the "Header" versioning approach in the event
that the version was not specified or for some 'Legacy' API methods that
could be mapped to a version purely based on the routeTemplate