Use vanilla otel or honeycomb otel distro in all services

[VinozzZ]

Currently, services in the example are using a mix of beeline, otel distro, or vanilla otel library. Since beeline is being sunset, we should at least refresh those examples with either otel distro or vanilla otel.

.NET

• frontend using Honeycomb.OpenTelemetry
• message-service using Honeycomb.OpenTelemetry
• name-service using OpenTelemetry
• dotnet year-service using OpenTelemetry #967

Elixir

• frontend using opentelemetry-erlang
• message using opentelemetry-erlang
• name using opentelemetry-erlang
• year using opentelemetry-erlang

Go

• frontend using opentelemetry-go
• message-service using beeline-go
• name-service using opentelemetry-go
• year-service using honeycomb-opentelemetry-go #968

Java

• frontend using opentelemetry-javaagent
• message-service using honeycomb-opentelemetry-javaagent
• name-service using honeycomb-opentelemetry-javaagent
• java year-service using honeycomb-opentelemetry-sdk #969

Node

• frontend using opentelemetry-js
• message-service using beeline-nodejs
• name-service using beeline-nodejs
• year-service using opentelemetry-js #970

Python

• frontend using beeline-python
• message-service using opentelemetry-python
• name-service using honeycomb-opentelemetry
• update python year-service to use vanilla otel #971

Ruby

• frontend using opentelemetry-ruby
• message-service using beeline-ruby
• name-service using beeline-ruby
• year-service using beeline-ruby; switch to OTel #966

Web

• A web app instrumented using opentelemetry-js