Move capture_message_content kwarg logic to genai-utils

[rads-1996]

Description

The opentelemetry-instrumentation-genai-openai-agents package carried its own _resolve_content_mode helper to translate a capture_message_content kwarg into a ContentCapturingMode (handling enum/bool/string aliases and falling back to the OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT env var). This change lifts that logic into opentelemetry-util-genai as a shared resolve_capture_message_content() helper so every GenAI instrumentation can adopt the same kwarg pattern without copying the code. The ContentCapturingMode enum also gains capture_in_span / capture_in_event properties so callers no longer need to hard-code which modes imply span vs. event capture.

opentelemetry-instrumentation-genai-openai-agents
Breaking Change - Previous behavior: Previously when neither the kwarg nor the env var were set, content capture defaulted to SPAN_AND_EVENT.

New Behavior: Like other instrumentations when neither the kwarg nor the env var were set, content capture is defaulted to NO_CONTENT. Users who want sensitive content captured must opt in explicitly via the env var or the new kwarg.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. List any relevant details for your test
configuration.

• Unit tests

Checklist

See CONTRIBUTING.md
for the style guide, changelog guidance, and more.

• Followed the style guidelines of this project
• Changelog updated if the change requires an entry
• Unit tests added
• Documentation updated

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Centralizes and standardizes “message content capture” resolution across GenAI instrumentations by introducing a shared resolver, and consolidates capture-mode semantics into the shared ContentCapturingMode type.

Changes:

• Added resolve_capture_message_content(...) helper with alias support and warning-on-unknown behavior.
• Added capture_in_span / capture_in_event properties to ContentCapturingMode and migrated OpenAI Agents to use the shared enum.
• Updated and expanded tests; adjusted OpenAI Agents tests to set a default capture mode and removed coverage tests for deleted private resolver.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
util/opentelemetry-util-genai/tests/test_utils.py	Adds unit tests for the new capture-mode resolver and enum properties.
util/opentelemetry-util-genai/src/opentelemetry/util/genai/utils.py	Introduces the shared resolve_capture_message_content resolver and alias map.
util/opentelemetry-util-genai/src/opentelemetry/util/genai/types.py	Adds helper properties for capture-in-span / capture-in-event checks.
instrumentation/opentelemetry-instrumentation-genai-openai-agents/tests/test_zz_coverage_improvements.py	Removes tests for deleted _resolve_content_mode and updates coverage note.
instrumentation/opentelemetry-instrumentation-genai-openai-agents/tests/test_tracer.py	Sets default capture_message_content for tests that assert captured content.
instrumentation/opentelemetry-instrumentation-genai-openai-agents/src/opentelemetry/instrumentation/genai/openai_agents/span_processor.py	Switches to shared ContentCapturingMode and provides a compatibility alias.
instrumentation/opentelemetry-instrumentation-genai-openai-agents/src/opentelemetry/instrumentation/genai/openai_agents/init.py	Replaces local resolver/env handling with shared resolve_capture_message_content.

[rads-1996]

Do we still want to allow for such flexibility or make it more stricter?