[OTEL] Improve span operation/description generation

[AbhiPrasad]

Currently our span transformation from otel -> sentry (and generation of span operation/description) works relatively well for http and db spans, but could be improve for other span types. This is a tracking issue to record various improvements we could make to this with the intention to improve our various demos.

In the future we'll be bringing this to Relay - but step by step!

Node

• We should set otel.kind to be a string instead of an integer: https://sentry-sdks.sentry.io/performance/otel-demo-paymentservice:d8ed7fb857b34878b032386ef5efb665 fix(otel): Make otel.kind be a string sentry-javascript#7182

Go

• Re-evaluate how we set operation/description for messaging spans: https://sentry-sdks.sentry.io/performance/otel-demo-checkoutservice:3a93068eca0d4acb9c7865f68ba5183f

• Set better http.client description: https://sentry-sdks.sentry.io/performance/otel-demo-checkoutservice:3a93068eca0d4acb9c7865f68ba5183f

• Otel context does not appear for some events: https://sentry-sdks.sentry.io/performance/otel-demo-productcatalogservice:79647993367f4ef2995bf815e1e8e0c7
  Should be fixed by feat(tracing): Introduce span.SetContext sentry-go#599, fix: Introduce a new Span.Name field sentry-go#605

Java

• We should set rpc span operation: https://sentry-sdks.sentry.io/performance/otel-demo-adservice:f42846606929401c9b9f4cfb0fff4724/ Set operation for RPC calls recorded via OpenTelemetry sentry-java#2540

Ruby

• We should use template.render for Sinatra templates: https://sentry-sdks.sentry.io/performance/otel-demo-emailservice:93ab62e7d4ac4eb0994a0976e565cf23 (could we generalize to other template rendering?)

Python

• Set rpc span operation: https://sentry-sdks.sentry.io/performance/otel-demo-recommendationservice:365904f069654d7fa3915df69d3c08bc