feat(graphql): add exception tracking graphql span

[quinna-h]

Add exception tracking on graphql span event with the following attributes:

• exception.type
• exception.message
• exception.escaped
• exception.stacktrace

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:

ddtrace/contrib/internal/graphql/patch.py                               @DataDog/apm-core-python @DataDog/apm-idm-python
tests/snapshots/tests.contrib.graphql.test_graphql.test_graphql_fail.json  @DataDog/apm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: quinna.halim/add-exception-tracking-graphql-span
Commit report: bc6ee5a
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1184 Skipped, 1m 39.43s Total Time

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-21 22:12:18

Comparing candidate commit bc6ee5a in PR branch quinna.halim/add-exception-tracking-graphql-span with baseline commit 0249aa7 in branch main.

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