go.mod: retract experimental versions

[darccio]

What does this PR do?

Retracts some tagged versions created to dogfood our v1 shim for v2.

Motivation

Keep public docs clean and let users to use release candidates if they want without go get pulling the experimental versions accidentally.

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.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-08-05 10:22:07

Comparing candidate commit c9f2fbd in PR branch dario.castane/retract-experimental-versions with baseline commit 794b629 in branch main.

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

[nsrip-dd]

With this PR, we won't need the hack in the Orchestrion CI, right? https://github.com/DataDog/orchestrion/blob/6feff0e769815269d892e16c6b59d26ba6304f8f/.github/workflows/deps-update.yml#L28-L35

[darccio]

With this PR, we won't need the hack in the Orchestrion CI, right? DataDog/orchestrion@6feff0e/.github/workflows/deps-update.yml#L28-L35

Indeed, it won't be more needed.