Add support to OpenTelemetry semantic conventions

We should have a printer that supports [Elastic Common Schema](https://www.elastic.co/guide/en/ecs/current/index.html)

The issue names no files, tests, or entry points; begin by locating Tracee's existing printer or output-format implementation and reviewing the linked Elastic Common Schema documentation. Clarify whether the target is OpenTelemetry semantic conventions, Elastic Common Schema, or both, then define the supported fields and verify the printer output against representative events.

Written by the indexing model from the issue text.