feat(registry): emit resolve usage-telemetry event (Spec 015)

[enricopiovesan]

Summary

• Instruments resolve_version_range (the caret-range/semver resolution
  path used by registry sync and equivalent callers) to accept an
  optional ResolveTelemetry<'a> — a UsageTelemetrySink (from
  traverse-contracts) paired with a caller-supplied resolved_at
  timestamp, so this crate never depends on a wall clock or gains new
  dependencies (matches every other registered_at-style field already in
  this crate).
• On a successful resolution, if a sink was supplied, it is invoked exactly
  once with a resolve event carrying {capability_id}@{version} and
  nothing else. A failed or ambiguous resolution never invokes it. Omitting
  the parameter (None) is byte-for-byte identical to the pre-existing
  behavior.
• Left the crate's internal transitive-dependency walk
  (dependency_resolver.rs's own call into resolve_version_range)
  untelemetered — spec 015 FR-006 explicitly restricts this spec to the
  top-level resolution path, not a further behavior change.
• Bumps the pinned traverse-contracts dependency resolution to 0.9.1
  (already permitted by the existing >=0.8.1, <0.10.0 range in
  Cargo.toml) to pick up the UsageTelemetrySink trait, now that
  traverse-framework/traverse#927 has shipped and published it —
  unblocking this ticket.
• Bumps traverse-registry to 0.15.0 (existing public function signature
  changed shape).

Closes #145.

Governing Spec

• 015-runtime-usage-telemetry-resolve-hook
• 010-crate-publish-pipeline

Project Item

Registry Project — issue #145

Definition of Done

• crates/traverse-registry's public resolution API accepts an optional UsageTelemetrySink parameter; omitting it produces byte-identical behavior to today.
• A successful resolution with a sink supplied invokes it exactly once with the correct namespace/id@version and nothing else.
• A failed/ambiguous resolution never invokes the sink.
• No new dependency beyond the version-bumped traverse-contracts (cargo tree -p traverse-registry shows no new crate).
• New patch/minor version of traverse-registry published per this repo's crate-publish pipeline (spec 010).

Validation

• cargo test -p traverse-registry --locked (184 lib + 94 application_manifest + 10 connector_activation + 130 other integration tests, all passing — including new SC-001/SC-002/SC-003 unit tests)
• cargo clippy -p traverse-registry --all-targets --locked -- -D warnings
• cargo tree -p traverse-registry reviewed manually — dependency set unchanged beyond traverse-contracts 0.8.1 → 0.9.1
• python3 scripts/ci/capability_validation.py

Test plan

• CI green
• Tag v0.15.0 and push to trigger publish-crate.yml after merge, per spec 010