feat: do not report error stack for status code errors

[hannahkm]

What does this PR do?

Motivation

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• New code is free of linting errors. You can check this by running ./scripts/lint.sh locally.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-08-05 17:33:50

Comparing candidate commit 5e13bf3 in PR branch hannahkm/new-error-tag with baseline commit 80c9990 in branch main.

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

scenario:BenchmarkSetTagString-24

• 🟥 execution_time [+5.024ns; +8.376ns] or [+4.474%; +7.458%]

[hannahkm]

takeStacktrace is now being called from line 449 to calculate the handling stack. In order to avoid double counting how many errors are relying on takeStacktrace to get the error stack, we move the telemetry counter from line 466 to here.