chore(vendor): sync LiteLLM streaming latency attempt attrs

[sayonfortify]

Carries the fr-openllmetry-py LiteLLM streaming-latency fix from tag fr-v0.52.6.30 into the vendored ocelle tree.

What changed:

• Vendor manifest now points at fr-openllmetry-py tag fr-v0.52.6.30 / commit 02adf494.
• LiteLLM streaming safety wrappers copy TTFT/STTG attrs to the canonical active retry-attempt span.
• The canonical fortifyroot.litellm.attempt_N span now receives:
  • fortifyroot.llm.streaming.time_to_first_token_ms
  • fortifyroot.llm.streaming.time_to_generate_ms
• VENDOR_DEPENDENCIES refresh is from the official vendor.sh run.

Why:

• Backend canonicalization keeps the LiteLLM attempt span, not the wrapper span.
• The fr-system-tests exact-once framework topology gate exposed that TTFT/STTG could be present on the skipped wrapper while the canonical usage event had no streaming latency.

Validation:

• ./scripts/vendor.sh ../fr-openllmetry-py . fr-v0.52.6.30
• python3 -m py_compile on changed vendored files
• conda run -n py3.12 python -m pip install -e .
• conda run -n py3.12 python -m pytest tests/test_vendored_imports.py -q -> 34 passed
• With this local ocelle checkout installed, targeted fr-system-tests passed:
  FR_PROVIDER_MODE=fixture ./scripts/run-tests.sh --telemetry -- -k 'streaming_latency_litellm_single_canonical_usage_event or streaming_latency_llamaindex_single_canonical_usage_event' -rs
  -> analytics_roundtrip 2 passed; overall 13 suites passed, 0 failed