go.mod: replace mapstructure and parseutil

[eliottness]

What does this PR do?

• Replace github.com/hashicorp/go-secure-stdlib/parseutil with strconv
• Replace github.com/mitchellh/mapstructure with github.com/go-viper/mapstructure/v2
• Run find -name go.mod -execdir go mod tidy \;

Motivation

• Fixes [BUG]: Usage of archived go-module #3303
• Remove github.com/hashicorp/go-secure-stdlib/parseutil

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.
• 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.
• For internal contributors, a matching PR should be created to the v2-dev branch and reviewed by @DataDog/apm-go.

Unsure? Have a question? Request a review!

[datadog-datadog-prod-us1]

Datadog Report

Branch report: eliottness/update-deps
Commit report: ee1c541
Test service: dd-trace-go

✅ 0 Failed, 4493 Passed, 65 Skipped, 23m 21.74s Total Time

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-03-27 09:00:43

Comparing candidate commit 7e7abef in PR branch eliottness/update-deps with baseline commit 0b8b4d6 in branch v2-dev.

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

scenario:BenchmarkStartSpan-24

• 🟥 execution_time [+71.245ns; +92.755ns] or [+2.989%; +3.891%]

[kakkoyun]

LGTM