feat(telemetry): implement custom serialization for telemetry ids

[Nemo157]

Add custom Display, FromStr, Serialize, and Deserialize implementations for ProcessId, ThreadId, and SpanContext types.

These provide a consistent hex-encoded string format with colon separators for composite IDs (process:thread for ThreadId, process:span for SpanContext). This makes telemetry ids more readable and provides a unified format for logging and serialization.

[github-actions]

Deployment - Branch link	Commit link - 2046db2
user-manual preview	https://c356307e.user-manual-2bd.pages.dev
private-docs preview	https://4ec49d7d.private-docs-3bh.pages.dev
veecle-telemetry-ui preview	https://08b9a88b.veecle-telemetry-ui.pages.dev

[codecov]

Codecov Report

❌ Patch coverage is 65.36585% with 71 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
veecle-telemetry/src/id.rs	75.93%	25 Missing and 7 partials ⚠️
veecle-telemetry/src/protocol.rs	51.61%	23 Missing and 7 partials ⚠️
veecle-telemetry-ui/src/store/mod.rs	0.00%	4 Missing ⚠️
veecle-telemetry-ui/src/ui/selection_panel.rs	0.00%	4 Missing ⚠️
veecle-telemetry-ui/src/ui/timeline/traces.rs	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[claude]

Change Summary

This PR adds custom Display, FromStr, Serialize, and Deserialize implementations for telemetry ID types (ProcessId, ThreadId, SpanContext). The implementation provides a unified hex-encoded string format with colon separators for composite IDs (e.g., process:thread for ThreadId, process:span for SpanContext), improving readability in logs and serialization. The UI components have been updated to use these new Display implementations instead of Debug formatting.

---

Issues Found

Found 3 issues that should be addressed:

🔴 Critical

1. Variable naming issue in SpanContext::deserialize (veecle-telemetry/src/id.rs:299-300) - Variable named thread should be span since it represents a SpanId, not a ThreadId. This appears to be copy-pasted from the ThreadId implementation.

🟡 Important

2. Inconsistent error message (veecle-telemetry/src/id.rs:292) - Error message says "byte 33" but the check is bytes[32]. Should use consistent indexing terminology.

3. Same error message issue (veecle-telemetry/src/protocol.rs:202) - Same inconsistency in the ThreadId deserialization.

All issues have inline comments with suggested fixes.

[HectorMRC]

LGTM