fix(metrics): drop otel_scope_info, expose scope as labels

The otel prometheus exporter v0.59.0 stopped emitting the standalone
otel_scope_info metric. Scope identity is now carried by
otel_scope_name, otel_scope_version, and otel_scope_schema_url
labels on every metric, added in v0.58.0. The bump to v0.65.0 in
this branch crosses that boundary, so the t0119 baseline failed.

Update the sharness baseline, docs/metrics.md, and add a v0.42
changelog highlight so operators scraping otel_scope_info know to
switch their dashboards to the per-metric labels.

Author: lidel

docs/changelogs/v0.42.md

@@ -11,6 +11,8 @@ This release was brought to you by the [Shipyard](https://ipshipyard.com/) team.
 - [Overview](#overview)
 - [🔦 Highlights](#-highlights)
   - [🐛 Fixed pin operations hanging under pinned reprovide strategies](#-fixed-pin-operations-hanging-under-pinned-reprovide-strategies)
+  - [📊 OpenTelemetry: scope info now exposed as labels](#-opentelemetry-scope-info-now-exposed-as-labels)
+  - [📦️ Dependency updates](#-dependency-updates)
 - [📝 Changelog](#-changelog)
 - [👨‍👩‍👧‍👦 Contributors](#-contributors)
 
@@ -24,6 +26,15 @@ This release was brought to you by the [Shipyard](https://ipshipyard.com/) team.
 
 The pinner now snapshots the index under the read lock and releases it before the reprovider starts, so pin operations are no longer blocked by the reprovide cycle. The default `Provide.Strategy=all` was not affected.
 
+#### 📊 OpenTelemetry: scope info now exposed as labels
+
+The Prometheus endpoint no longer emits the `otel_scope_info` metric. Each metric now carries `otel_scope_name`, `otel_scope_version`, and `otel_scope_schema_url` labels identifying the instrumentation library that produced it. Update dashboards or queries that read `otel_scope_info` to consume these labels instead. See [`docs/metrics.md`](https://github.com/ipfs/kubo/blob/master/docs/metrics.md) for details.
+
+#### 📦️ Dependency updates
+
+- update `go-libp2p-pubsub` to [v0.16.0](https://github.com/libp2p/go-libp2p-pubsub/releases/tag/v0.16.0)
+- update `go-fuse/v2` to [v2.10.1](https://github.com/hanwen/go-fuse/releases/tag/v2.10.1)
+
 ### 📝 Changelog
 
 ### 👨‍👩‍👧‍👦 Contributors

docs/metrics.md

@@ -121,5 +121,5 @@ These metrics are automatically added to Gateway handlers, Hostname Gateway, Lib
 
 Kubo uses Prometheus for metrics collection for historical reasons, but OpenTelemetry metrics are automatically exposed through the same Prometheus endpoint. These metadata metrics provide context about the instrumentation:
 
-- `otel_scope_info` - Information about instrumentation libraries producing metrics
+- `otel_scope_name`, `otel_scope_version`, `otel_scope_schema_url` - Per-metric labels identifying the instrumentation library that produced each metric
 - `target_info` - Service metadata including version and instance information