Add support to view a particular trace from open search in a trace view

[sarahzinger]

Depends on completion of #105 first

The goal here is to be able to type in a lucene query for a particular trace (something like this maybe, not sure on the groupby bits):

and then return back information about that trace that can be viewed in the Traces visualization, see example from X-ray plugin:

It's possible this work might be best split up into multiple tickets, and that there might be a few unforeseen additional things we'll need to do, but I suspect the work here will generally involve:

• adding a "Trace" option to the query editor
• setting it so that when a user selects the trace option and passes a trace id, it calls the /_msearch endpoint with the correct arguments so that we get all spans for a particular trace id, see https://docs.google.com/document/d/1l8HYKvCddF9jUdkAV0TkHU6fsWFs8T1s-gLWbaGLtog/edit
• then figuring out how to format the data into a data frame so that the Traces visualization can parse this and show the right visualization (will likely want to look at X-Ray to see how this is done)

[sarahzinger]

slightly blocked by #105 but I think it's actually fairly easy to set up an open search instance locally with traces, we're just stuck on putting it in the AWS OpenSearch Service atm

[sarahzinger]

realizing this one might be a bit easier to start with: #107 so I'm going to start on this one. But I think anyone could still pick this up and start looking into how to map a trace to the traces visiualization

[sarahzinger]

@idastambuk is a bit blocked on this since I'm still working on the query to get all traces, but she's going to try first rendering the traces visualization with mock data to see if we know what we need to query for.

[taleena]

This was done in Apr and counted there.