Backend: Implement Lucene Traces in the backend

[sarahzinger]

There's currently no processing of traces on the backend, only frontend. There is no equivalent PR in ElasticSearch to reference, but we have implemented this fairly recently so there are up-to-date tests and the feature looks stable.

Tasks

Preview Give feedback

1. Migrate trace list query building #280
   effort/medium +1
   
2. Migrate trace list response processing #287
   effort/medium +1
   
3. Trace spans: Migrate query and response processing to the backend #303
   effort/medium +1
   

Note: This is the case for jaeger trace format, as otel hasn't been implemented yet (#205). However, the scope of this PR is just migrating the data processing for jaeger traces that we currently have in FE and in data-prepper.

Some general guidelines are:

• Create visualization to compare between frontend and backend flows, preferably in a shared Cloud dashboard e.g. clouddatasources.grafana.net
• Unit tests in the frontend should be copied or updated in the backend to assert the same behavior and add unit tests when there are none.
  • Check Elasticsearch repo for related tests – helpful when there are no OpenSearch tests in the frontend or backend
• We should match OpenSearch's backend behavior to the current frontend behavior, but be aware it may not always make sense. Elasticsearch's current behavior is also another resource for how OpenSearch should behave.
  • Let's be pragmatic about this – our foremost goal is the migration of OpenSearch's frontend behavior. We can aim for some Elasticsearch feature parity, but only within reason.
• Migrate or implement: i.e. make any changes to code in backend
• Use the dashboard created above to compare visualization results (data frame comparison)
  • Can also inspect data frame on a more detailed basis