fix: align semconv import with OTel SDK schema URL (#101)

Controller pods crash on startup with:

  Failed to initialize OTel MeterProvider
  error: building OTel resource: conflicting Schema URL:
    https://opentelemetry.io/schemas/1.40.0 and
    https://opentelemetry.io/schemas/1.26.0

resource.Merge rejects merging resources whose schema URLs differ.
resource.Default() reports schema v1.40.0 (embedded in the SDK at
v1.43.0), while cmd/telemetry.go hardcoded semconv/v1.26.0 as the
schema for the custom resource overlay.

Bump the semconv import to v1.40.0 so the two schema URLs agree.
All three symbols in use here (semconv.SchemaURL, ServiceName,
ServiceVersion) are stable across semconv versions — drop-in
substitution.

Unblocks the controller image bump that #100 landed. Post-#99
controller pods stop CrashLoopBackOff and roll out cleanly, which
in turn unblocks SeiNodeDeployment.status.internalService for the
autobake workflow.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: bdchatham

cmd/telemetry.go

@@ -11,7 +11,7 @@ import (
 	promexporter "go.opentelemetry.io/otel/exporters/prometheus"
 	sdkmetric "go.opentelemetry.io/otel/sdk/metric"
 	"go.opentelemetry.io/otel/sdk/resource"
-	semconv "go.opentelemetry.io/otel/semconv/v1.26.0"
+	semconv "go.opentelemetry.io/otel/semconv/v1.40.0"
 	crmetrics "sigs.k8s.io/controller-runtime/pkg/metrics"
 )