fix: set span error metadata only for escaped errors

[dubloom]

Before this change we set some span error metadata for every call of record_exception. This would set the span as an errored span. However, we can call several times record_exception within a span and we can pass handled exceptions as arguments. In the later case, we want the span not to be errored.

This change aims at addressing this. We will set the relevant metadata only if the error is escaped (which means unhandled).

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

releasenotes/notes/fix-otel-record-exception-api-17f3a4b23948ec79.yaml  @DataDog/apm-python
ddtrace/internal/opentelemetry/span.py                                  @DataDog/apm-sdk-api-python
tests/snapshots/tests.opentelemetry.test_trace.test_otel_start_span_record_exception.json  @DataDog/apm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: dubloom/fix-otel-record-exception
Commit report: dea936a
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1468 Skipped, 4m 29.24s Total duration (35m 10.64s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-17 08:57:29

Comparing candidate commit b4e22fb in PR branch dubloom/fix-otel-record-exception with baseline commit 0c7fc1b in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 418 metrics, 2 unstable metrics.

[mabdinur]

I clean up the commit history and left one suggestion.

Overall looks good to me!