Replace the "movement_timing" tracing target and the logging layer
it targeted with an optionally installed OpenTelemetry OTLP exporter.
The name of the tracing target matched to send OpenTelemetry events is
"movement_telemetry".

Add the telemetry overlay enabling OTLP telemetry
export in suzuka-full-node and m1-da-light-node..

In the telemetry overlay for suzuka-full-node, add
an OTLP collector start job running a docker container.

Provide telemetry API as separate from tracing rather than
a globally installed layer. Installing an OpenTelemetry layer into the
global tracing subscriber raises nasty reentrancy issues because
the OTLP exporter stack also uses tracing under the hood.

Install an OpenTelemetryLayer configured with the OTLP exporter.
The tracing spans and events to export are selected by target
"movement_telemetry".

The implementation of shutdown in the opentelemetry_sdk exporter
calls futures_executor::block_on, which does not play well with
the multithreaded Tokio runtime.

OpenTelemetry needs spans at the top level of
its log event model at least.

Emit telemetry events detailing the success or failure

In the transaction_ingress task of suzuka-full-node
and executor's transaction_pipe, add comments detailing
which metrics the telemetry events are contributing to.

At the points where transaction is dropped in the submit_transaction
method, emit telemetry events. These will help compute the
transaction failure rate.

Apply the telemetry overlay when running tests in the local setup.

Port the simple jaeger setup from process-compose.