fix(kafka): catch typeerror during tombstone tagging

[emmettbutler]

This pull request resolves #8016 by catching an error that can occur during message consumption due to confluentinc/confluent-kafka-python#1192.

Checklist

• Change(s) are motivated and described in the PR description
• Testing strategy is described if automated tests are not included in the PR
• Risks are described (performance impact, potential for breakage, maintainability)
• Change is maintainable (easy to change, telemetry, documentation)
• Library release note guidelines are followed or label changelog/no-changelog is set
• Documentation is included (in-code, generated user docs, public corp docs)
• Backport labels are set (if applicable)
• If this PR changes the public interface, I've notified @DataDog/apm-tees.
• If change touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.

Reviewer Checklist

• Title is accurate
• All changes are related to the pull request's stated goal
• Description motivates each change
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Change is maintainable (easy to change, telemetry, documentation)
• Release note makes sense to a user of the library
• 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

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: emmett.butler/kafka-typeerror
Commit report: abb2f44
Test service: dd-trace-py

✅ 0 Failed, 101 Passed, 219 Skipped, 1m 41.23s Total duration (25m 24.57s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-02-23 18:41:11

Comparing candidate commit c1633a8 in PR branch emmett.butler/kafka-typeerror with baseline commit 17ae9b2 in branch main.

Found 2 performance improvements and 3 performance regressions! Performance is the same for 198 metrics, 9 unstable metrics.

scenario:coreapiscenario-set_item

• 🟥 max_rss_usage [+652.969KB; +801.931KB] or [+2.233%; +2.742%]

scenario:otelspan-start

• 🟩 max_rss_usage [-4.391MB; -4.286MB] or [-8.780%; -8.570%]

scenario:samplingrules-average_match

• 🟥 max_rss_usage [+806.961KB; +956.777KB] or [+2.777%; +3.293%]

scenario:samplingrules-high_match

• 🟥 max_rss_usage [+922.494KB; +1041.538KB] or [+3.181%; +3.592%]

scenario:span-add-metrics

• 🟩 max_rss_usage [-25.891MB; -25.758MB] or [-39.860%; -39.656%]

[github-actions]

The backport to 2.4 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.4 2.4
# Navigate to the new working tree
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport-8506-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cf942b45c453ca835755f6dc6c2d2a2346d98618
# Push it to GitHub
git push --set-upstream origin backport-8506-to-2.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport-8506-to-2.4.