Modify query building and response processing to support raw Jaeger traces

[idastambuk]

Raw jaeger traces have some fields stored under different names. For example operationName instead of name. This means we have to modify our queries to aggregate different fields, as well as modify response processing for service map + traces in general to target different fields and store them in grafana-recognizable format (for displaying spans, for example).
There's still an open question about how we should detect if we're querying Jaeger or Data Prepper data. Open Search Dashboards solve this by having a dropdown and building queries on the basis of that:

We currently don't have a test app for this, so that should be the first step.