Make OpenAI span data OTel compatible

[antonpirker]

Make sure all OpenTelemetry semantic conventions for AI clients and also the Sentry Conventions are adhered to.

Also cleans up the code a bit for better readability/maintenance.

[codecov]

Codecov Report

❌ Patch coverage is 78.04878% with 36 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.72%. Comparing base (5cc512f) to head (eb629de).
⚠️ Report is 1 commits behind head on antonpirker/openai-overhaul.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
sentry_sdk/integrations/openai.py	83.33%	7 Missing and 15 partials ⚠️
sentry_sdk/utils.py	54.83%	12 Missing and 2 partials ⚠️

Additional details and impacted files

@@                       Coverage Diff                       @@
##           antonpirker/openai-overhaul    #4613      +/-   ##
===============================================================
+ Coverage                        80.68%   80.72%   +0.04%     
===============================================================
  Files                              156      156              
  Lines                            16579    16612      +33     
  Branches                          2814     2830      +16     
===============================================================
+ Hits                             13376    13410      +34     
- Misses                            2311     2313       +2     
+ Partials                           892      889       -3     

Files with missing lines	Coverage Δ
sentry_sdk/consts.py	94.66% <ø> (ø)
sentry_sdk/integrations/openai_agents/utils.py	80.24% <100.00%> (+7.43%)	⬆️
sentry_sdk/utils.py	87.01% <54.83%> (-1.22%)	⬇️
sentry_sdk/integrations/openai.py	84.25% <83.33%> (+2.74%)	⬆️

... and 6 files with indirect coverage changes

[sentrivana]

Looks like we have this check in each branch (maybe I'm mistaken), can we just move it after the whole if branch?

[sentrivana]

Actually, can we move it out of this function altogether and end the span after the call to this function? I'd not expect _set_output_data to do any actual span lifecycle management. And _set_input_data also doesn't start spans, so it's a bit inconsistent.

[antonpirker]

unfortunately we can not move this out. because the span is finished in the generators defined in this function. if we move the finish outside the span will be finished too early and not only after the decorator is finished iterating over.