Tracking: migrate OpenInference Python instrumentations into this repo

This issue tracks porting the OpenInference Python instrumentation packages into
opentelemetry-python-genai, so that GenAI instrumentation is built on the shared
opentelemetry-util-genai utilities and emits telemetry that conforms to the
GenAI semantic conventions.

[!IMPORTANT]

• Use the instrumentations from https://github.com/open-telemetry/donation-openinference/ as the source
  (once seeded). DO NOT use https://github.com/Arize-ai/openinference/.

• Before starting work on a specific library, please ask to be assigned in the table —
  for example, by leaving a comment on this issue.

• Prioritize packages with more downloads and the ones your organization is interested in.

• Make sure to link this issue from the migration PRs.

Candidate packages (ordered by recent PyPI downloads):

Migration guidance

• Build on opentelemetry-util-genai. Avoid emitting spans, metrics, or events directly — use the
  shared utilities so all packages produce consistent, conformant telemetry, share the same configuration
  options and extensibility hooks, and to reduce maintenance toil.
• Do use AI to help with the port and the review. Minimize use of AI when talking to humans.
• Use the provided migration and review skills (to be added in https://github.com/open-telemetry/opentelemetry-python-genai/pull/143) to drive the port consistently.
• Contribute back to the migration skills so the workflow improves as we go.
• If migration needs a design decision or some discussion, create individual issues for these
• Keep the PR scoped to the migration only. Do not instrument new operations and do not
  add new features beyond what the source instrumentation already does. Adding missing tests
  for the migrated behavior is encouraged.

Naming

• Package names follow the opentelemetry-instrumentation-genai-{lib} pattern, where {lib} is
  the PyPI name of the instrumented library — e.g. crewai →
  opentelemetry-instrumentation-genai-crewai, importing as
  opentelemetry.instrumentation.genai.crewai. This MAY be different from the suffix used by OpenInference.

Version support

• Consider supporting only the latest major version of the instrumented library and dropping
  compatibility with older versions, to reduce maintenance toil.

Existing packages

• For libraries that already have a package in this repo (marked "Existing package" above), do
  not re-port from scratch. Instead, analyze the delta between the OpenInference
  instrumentation and the existing code — operations covered, scenarios, attributes, captured
  content — and contribute only what's missing or improved back into the existing package.
  Do not modify existing code. If refactoring is helpful, do it as a follow-up to the migration PR.

Semantic conventions

• When there is no convention for a specific operation or scenario, file a bug in
  open-telemetry/semantic-conventions-genai
  to get it specified.
• In the meantime, report an empty span where appropriate (e.g. an operation span without
  speculative attributes). Do not report unconventional / non-spec attributes.
  Leave TODOs in the code pointing to the semconv issue.

Tests

• Add conformance tests for the important scenarios of each library:
  • LLM clients: inference + tool calling + reasoning + multi-modal content, embeddings.
  • Agents: invoke_agent + tools, workflows, orchestration.
• Add missing unit test coverage for the instrumentation logic (if anything is missing).

Ask to be assigned to one unclaimed package, then read its source in donation-openinference and the migration guidance in this issue, including CONTRIBUTING.md and the migration skills from PR #143. A package migration is done when it uses opentelemetry-util-genai, includes the required conformance and unit tests, and links this issue from its migration PR.