[CLEAN] Synthetic Benchmark PR #24717 - feat: distributed tracing - Part (1)

[tomerqodo]

Benchmark PR calcom#24717

Type: Clean (correct implementation)

Original PR Title: feat: distributed tracing - Part (1)
Original PR Description: ## What does this PR do?

Part of calcom#22969

• Splitting PR feat: distributed tracing  calcom/cal.diy#24055 - Part 1

This PR introduces a DistributedTracing utility class that enables cross-service request tracing by generating hierarchical trace/span IDs and propagating trace context through payloads.

• It provides contextual logging via getTracingLogger() that automatically includes trace metadata in log prefixes, and supports trace injection/extraction for maintaining trace continuity across service boundaries.

• The class uses a pluggable ID generator and integrates with tslog for structured logging with trace-enriched context.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• N/A I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Original PR URL: calcom#24717

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "[CLEAN] Synthetic Benchmark PR #24717 - feat: distributed tracing - Part (1)". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit