[CURATOR-695] Open Telemetry tracing
This changes adds an Open Telemetry tracing driver. To make this more effective, it also decomposes OperationTrace events so that the start and end of the event can be handled distinctly.
Curator's OperationTraces are mapped to OTel Spans. When an OperationTrace is started (created), a corresponding OTel span is started and made current. The span is closed when the OperationTrace is committed. OperationTrace members are mapped to OTel span attributes, and result codes are mapped to appropriate OTel representations.
Any Curator EventTraces are attributed to the current OTel span.
Any thoughts on how this looks @eolivelli ?
I have asked for review on the mailing list
also please check CI