[kafka-redis-messages] Update dependencies, align with OTel/DD best p…

[dineshg13]

…ractices

• Update Go OTel SDK to v1.33.0, dd-trace-go to v1.69.1, IBM/sarama
• Update Java Spring Boot to 3.2.5, Kafka clients to 3.7.0, Jedis to 5.1.2
• Update OTel Java API to 1.36.0, Gradle to 8.6
• Migrate DD variant to IBM/sarama and redis/go-redis/v9
• Align with OTel messaging semantic conventions (span naming, attributes)
• Add W3C Trace Context + Baggage composite propagator for correct context propagation
• Add proper OTel SDK initialization with resource attributes and graceful shutdown
• Switch from raw Jedis to JedisPool for connection pooling in all Java variants
• Add Redis connection pool configuration in Go (PoolSize, MinIdleConns)
• Add health checks for all services in docker-compose files
• Add resource limits (memory) to all docker-compose services
• Standardize Dockerfiles with multi-stage builds and distroless base images
• Add .env.example documenting required DD_API_KEY
• Improve Kafka consumer error handling and graceful shutdown (SIGTERM)
• Add DD-specific comments explaining trace context mapping and configuration
• Document DD_TRACE_OTEL_ENABLED and DD_TRACE_PROPAGATION_STYLE settings
• Standardize application.properties across all variants

What does this PR do?

Motivation