Add OTLP log endpoint to convert log events to span annotations

[making]

This is the first pull request that fixes gh-21.
More use case tests, optimizations and options will be added later.

How to check UI locally

# Build the docker image
build-bin/docker/docker_build openzipkin-contrib/zipkin-otel:test
# Run the docker image
docker run --rm -p 9411:9411 docker.io/openzipkin-contrib/zipkin-otel:test

Run the example script using OpenAI+Python

cd collector-http/src/test/resources/python

python3 -m venv .venv
source .venv/bin/activate
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:9411
export OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true
export OPENAI_API_KEY=sk-YOUR_API_KEY
./run.sh
cd -

Run the example script using OpenAI+NodeJs

cd collector-http/src/test/resources/nodejs

export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:9411
export OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true
export OPENAI_API_KEY=sk-YOUR_API_KEY
./run.sh
cd -

a screenshot and trace data is attached here

[codefromthecrypt]

pretty cool to do real integration tests (with python and js), though maybe it could be less maintenance to send these signals directly in the integration test with otel java libs.

I don't recall the current state of java and the otel logs api, but yeah pretty sure it can be done directly.

This sort of change is optional until maintaining the examples becomes troublesome. Also, we can drop one of the example languages if the other becomes a problem.

Aside: one configuration I would expect to come quickly is to use solely the "event.name" as the annotation value, so like probably via ENV.

Finally, seems like this is really getting to the point where we need a README, to describe how each signal is translated. e.g. traces (translated) metrics (dropped) logs (recorded as annotations if have a span context and event name)

[codefromthecrypt]

Not sure it works, but prefer Map.of stuff if it is usable. that or just a multi-line json literal. We can use a later JDK in tests than we do for the compiled binary (floor JRE version). This can be done later.

[making]

Currently this project is compiled with Javav 8, probably just as it was when you scaffolded it.

Is there any reason to use this version? Would there be any problems with changing the base to Java 17?

[making]

Aside: one configuration I would expect to come quickly is to use solely the "event.name" as the annotation value, so like probably via ENV.

addressed in cb7a0dc

I don't recall the current state of java and the otel logs api, but yeah pretty sure it can be done directly.

When I checked, it didn't seem to be supported in Java. If it's supported at the next time I review it, I'll switch to the Java SDK version.
At this time, I've added nodejs and python because I have very little knowledge of this feature and I wanted to test whether it works for your intended usecases.

[codefromthecrypt]