fix(profiling): fix encoding-related issues in stack v2

[sanchda]

This adjusts the stack V2 API in order to conform to the new proposed echion renderer. This also fixes an encoding error in stack V2 which was caused by the old task renderer.

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.

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: sanchda/stack_v2.fix_tasks
Commit report: 1a0c153
Test service: dd-trace-py

✅ 0 Failed, 90 Passed, 1518 Skipped, 29m 52.14s Total duration (5m 7.3s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-07-05 17:15:21

Comparing candidate commit 1a0c153 in PR branch sanchda/stack_v2.fix_tasks with baseline commit df7fada in branch main.

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

[sanchda]

Moving this back into draft. There's some kind of issue in CI I didn't anticipate.

[sanchda]

Looks like the issue was spurious (and already seen in other PRs--not novel to this one), reopening.

[taegyunkim]

Looks like CI doesn't have DD_STACK_V2_REQUIRED set and build failures from these typos were not caught.

[github-actions]

The backport to 2.8 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.8 2.8
# Navigate to the new working tree
cd .worktrees/backport-2.8
# Create a new branch
git switch --create backport-9501-to-2.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 da759a93a772d88120f4983d7fdf8c34699152f2
# Push it to GitHub
git push --set-upstream origin backport-9501-to-2.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.8

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

[github-actions]

The backport to 2.9 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.9 2.9
# Navigate to the new working tree
cd .worktrees/backport-2.9
# Create a new branch
git switch --create backport-9501-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 da759a93a772d88120f4983d7fdf8c34699152f2
# Push it to GitHub
git push --set-upstream origin backport-9501-to-2.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.9

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