[FEATURE] Add support for OLTP telemetry #2956

Problem to solve

In order to gain more insight into the system, we should add the capability to trace traffic between components.

Proposed solution or feature

Add support via the otlp go library

• Add tracing to the executor
• Inject W3C headers for the Engine JSON-RPC (to allow for tracing between ev-node -> ev-reth )
• Add tracing to DA client
• Identify any additional components that would benefit from tracing.

Alternatives considered

No response

Additional context

No response

Implementation PRs

• feat: adding tracing for Executor and added initial configuration #2957 - Initial tracing configuration and executor tracing
• feat(tracing): add tracing to EngineClient #2959 - EngineClient tracing
• feat(tracing): adding eth client tracing #2960 - Eth client tracing
• feat(tracing): adding tracing to DA client #2968 - DA client tracing
• feat(tracing): Add Store, P2P and Config tracing #2972 - Store, P2P and Config tracing
• feat(tracing): adding block production tracing #2980 - Block production tracing
• chore: adding syncing tracing #2981 - Syncing tracing
• feat(tracing): tracing part 9 sequencer #2990 - Sequencer tracing
• feat(tracing): part 10 da retriever tracing #2991 - DA retriever tracing
• chore: adding tracing for da submitter #2993 - DA submitter tracing
• feat(tracing): adding forced inclusion tracing #2997 - Forced inclusion tracing
• feat(tracing): HTTP propagation #3000 - HTTP propagation
• feat(tracing): add store tracing #3001 - Store tracing