Update coordinator to support multiple config generations

[michaeldmitry]

Issue

Fixes #101
In preparation to use 2.7.1 tempo rock in Tempo-worker, we need to do some changes in the coordinator to be able to serve different configs depending on the workload version the worker is running.

Solution

• Define a default pydantic model scheme (to work with all workers before 2.7.1) and a 2.7.1 scheme
• Instead of generating the config blindly, pass the responsibility to a TempoConfigBuilderFactory to retrieve the correct config builder depending on the workload version sent from the workers.

Context

For backwards compatibility:

• keep jaeger_thrift_http

Drive-bys

• Explicitly add 0.0.0.0:port for all receivers
• Add otlp_http as a workload tracing protocol

Testing Instructions

• This CI passing tests for backward compatibility that the upgraded worker will still work with an outdated worker.
• Run itests for this coordinator with this worker