Service map phase II

[nehaduggal]

For the next version of service maps, here are a couple of additional use cases we want to cover:

• Show health indicators on service maps. If a service triggered an alert, surface the status of the service based on the triggered alert on the maps so I can determine what services are not healthy.
• If machine learning is configured for the service, surface the anomaly score indicator on the map to enable a user to detect an issue prior to it having a widespread impact(show more than just the critical anomaly scores)
• Allow a customer to switch between what health indicator to surface(default should be alert based)
• If no alerts or ML job is set up, prompt the user to set those up.

Related design issues:

• [APM] Design health indicators in service maps #222
• [APM] Alert annotation in Service maps #228

In addition here is a list of other UI modifications that we will address in this phase:

• Add info to connections between services [APM] Service map: Show information for connecting lines between nodes (edge metrics) kibana#52870
• address loading state on service popovers Eliminate loading spinner on service map popover kibana#59342
• handle map resizing on banner interactions Service map is not resized when dismissing banners kibana#56412
• support fullscreen mode APM Service Map fullscreen mode kibana#56531

[nehaduggal]

@ogupte @graphaelli