[Logs UI] Analysis log entry rate anomaly chart should provide a link to the ML UI

[Kerry350]

Summary

The log entry rate anomaly chart on the analysis results screen should provide a link to the ML UI so that users' can investigate things further within the specialised ML views if needed.

The placement of these buttons can be seen in #47201.

We can deep link to a single metric viewer for a single dataset by supplying the job_id, dataset name and time range.

The full link for the overall jobId would resemble the following, we need to worry about the jobIds and time parameters:

app/ml#/timeseriesexplorer?_g=(ml:(jobIds:!(kibana-logs-ui-default-default-log-entry-rate)),refreshInterval:(pause:!t,value:0),time:(from:'2019-10-14T09:47:15.000Z',to:'2019-10-14T09:47:15.000Z'))&_a=(mlSelectInterval:(display:Auto,val:auto),mlSelectSeverity:(color:%23d2e9f7,display:warning,val:0),query:(query_string:(analyze_wildcard:!t,query:'*')))

The full link for a specific event.dataset would look like the following, here we need to worry about the jobIds, time and mlTimeSeriesExplorer.entities parameters :

http://localhost:5601/chm/s/kerry/app/ml#/timeseriesexplorer?_g=(ml:(jobIds:!(kibana-logs-ui-kerry-default-log-entry-rate)),refreshInterval:(pause:!t,value:0),time:(from:'2019-09-19T23:33:26.000Z',to:'2019-10-14T09:45:00.000Z'))&_a=(mlSelectInterval:(display:Auto,val:auto),mlSelectSeverity:(color:%23d2e9f7,display:warning,val:0),mlTimeSeriesExplorer:(detectorIndex:0,entities:(event.dataset:redis.log)),query:(query_string:(analyze_wildcard:!t,query:'*')))

Acceptance criteria

• "Analyze in ML" buttons will exist that navigate to the relevant portions of the ML UI

[elasticmachine]

Pinging @elastic/infra-logs-ui