dev: Add OpenTelemetry Semantic Conventions Support

[pelageech]

OpenTelemetry Semantic Conventions

Currently, YDB Go SDK generates metrics and traces without following OpenTelemetry Semantic Conventions. This makes it difficult to standardize monitoring and observability across different applications and creates inconsistency with other database drivers.

Problem

• Current telemetry data lacks standardized naming conventions, this breaks compatibility when tied to telemetry names.
• Metrics and traces are not aligned with OpenTelemetry best practices
• Missing semantic conventions specific to YDB operations

Proposed Solution

1. Implement OpenTelemetry Semantic Conventions for database operations
2. Create YDB-specific semantic conventions following OTel guidelines
3. Maintain backward compatibility with existing telemetry
4. Contribute YDB semantic conventions to OpenTelemetry specification

Benefits

• Better integration with observability tools (Jaeger, Prometheus, etc.)
• Consistent naming across different database drivers
• Easier correlation of YDB operations with application traces
• Future-proof telemetry as OpenTelemetry becomes standard

References

• OpenTelemetry Database Semantic Conventions
• OpenTelemetry Go Instrumentation