## Why
When MCP binding capture or a catalog refresh is slow, separate spans
help identify whether the time went to startup, lock waits, or tool
catalog processing.
## What changed
- Trace server startup waits, catalog revision checks and snapshot
reads, and tool preparation and normalization.
- Trace catalog refresh lock waits, fetching, and publication, including
time spent waiting for active tool calls to finish.
- Record `cache_hit` on the binding capture span and trace the cache lock
wait. Box the catalog capture future on cache misses to keep it out of
callers' future layouts.
GitOrigin-RevId: e5a5c037455c755fe74ead9f0efabfcd7a9529bf