add weave tracer

[acured]

[ultmaster]

Generally I don't think it's necessary to support non-OTLP path for advanced tracers. You can first check whether the store has OTLP capability within init_worker(), which is added in a PR merged yesterday. If the store has such capability, you can use initialize the tracer so that it writes to the store.

You can inject the rollout_id and attempt_id if you have control over get_tracer(), or you can use the augmented OTLP exporter to modify the traces when export.