fix(examples-py): validate Pinecone, Pipecat, and Portkey OTel 2.x spans

[Nightingalelyy]

Summary

• Validate Pinecone, Pipecat, and Portkey OTel 2.x instrumentation with deterministic current-SDK scenarios and optional credential-gated live paths.
• Preserve one exact batch marker plus per-example identity, bounded semantic workflow inputs/outputs, and explicit client/worker/Respan teardown.
• Cover Pinecone sync/async/error operations, Pipecat offline/live/error pipelines, and Portkey sync/async/stream/tool/error behavior.

Validation

• Example contract tests pass: Pinecone 6/6, Pipecat 6/6, Portkey 6/6.
• Root-config Ruff check and format check pass for all three example directories.
• All 11 executed scenarios completed under otel2-fix-py-group-22-20260817T230705Z; optional live Portkey correctly skipped without PORTKEY_API_KEY.
• Respan MCP returned exactly 11 traces / 31 full records; all trees and details were inspected for roots, parents, IDs, content, model/provider, exact/non-estimated success usage, streaming, tools, failures, grouping, bounds, aliases, and credential leakage.
• Every full record carries the exact example_run_id and run_id; 31 log IDs and 31 span IDs are unique with no orphan or duplicate spans.
• Each runtime resolves its instrumentation package through the local editable Respan checkout.

External follow-ups

• Current ingestion still projects the native Pinecone 503 as success/200, leaves Portkey convenience tool arrays/provider ID incomplete, and estimates tokens on provider failures despite canonical package attributes.
• The outer decorated Pipecat and Portkey error workflow roots remain success/200 while package-owned descendants are correctly failed/401.
• Live Portkey routing/cache/retry coverage remains gated by the absent PORTKEY_API_KEY.

Companion examples

• respan #388