fix(telemetry): align resource identity across signals

[yordis]

• Operators need logs, metrics, and traces to identify the same node consistently during incident correlation.
• A single resource contract prevents signal-specific identity drift as instrumentation expands.

[cursor]

PR Summary

Low Risk
Observability resource metadata only; no changes to request handling, auth, or persistence.

Overview
Introduces TelemetryServiceIdentity as the single source for OpenTelemetry resource attributes (service.name, service.instance.id from the node component name, service.version).

Metrics and traces now use that identity via CreateResourceBuilder() instead of a local helper that only set name and version—so exported traces/metrics match logs on instance id for correlation. OTLP logs drop inline attribute dictionaries and use the same type.

ClusterVNode builds the identity from options.GetComponentName() and passes it into ClusterVNodeStartup; unit tests cover attribute/resource parity and rejection of blank component names.

^{Reviewed by Cursor Bugbot for commit 837d758. Bugbot is set up for automated code reviews on this repo. Configure here.}