chore(stacktrace): use internal/stacktrace package where possible

[kakkoyun]

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!

[kakkoyun]

• chore: ignore *.prof files #4153
• fix(stacktrace): keep SkipAndCaptureWithInternalFrames name visible in stacktraces #4152
• refactor(stacktrace): add captureStack helper for DRY capture logic #4151
• refactor(stacktrace): remove unused prefixTrie implementation #4150
• refactor(stacktrace): remove unnecessary locking from segmentPrefixTrie #4149
• perf(stacktrace): optimize parseSymbol with zero-allocation implementation #4148
• chore(stacktrace): use internal/stacktrace package where possible #4147 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-11-20 12:50:03

Comparing candidate commit 9865787 in PR branch kakkoyun/11-20-stacktrace-use_internalstacktrace_package_where_possible with baseline commit 1ed7e54 in branch main.

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

[kakkoyun]

Duplicate of #4062