Right now, the versioned route is where we read the version an incoming request. There are possible reasons (ex. 1, logging) for needing to know the request version earlier (or later) in the lifecycle outside of the route handler.
We should consolidate this logic so that Kibana only attempts to extract version as few times as possible (lazily, cached) and places it on the CoreKibanaRequest for other parts of the request lifecycle to see.
Right now, the versioned route is where we read the version an incoming request. There are possible reasons (ex. 1, logging) for needing to know the request version earlier (or later) in the lifecycle outside of the route handler.
We should consolidate this logic so that Kibana only attempts to extract version as few times as possible (lazily, cached) and places it on the
CoreKibanaRequest
for other parts of the request lifecycle to see.