[CI Visibility] Refactor gotesting integration to be used by orchestrion

[tonyredondo]

What does this PR do?

This PR is a refactor of the existing code so the new methods can be used by the orchestrion instrumentation. It doesn't introduce any new functionality and the existing tests are enough for testing the refactored code.

Motivation

Playing with orchestrion I realised that the current internal apis are really hard to call from an orchestrion integration, the refactor creates a new set of methods that can be easily called from methods prepend code kind of integrations.

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-09-06 11:02:11

Comparing candidate commit 6a4ca88 in PR branch tony/civisibility-refactor-for-orchestrion with baseline commit 50f9384 in branch main.

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

scenario:BenchmarkPartialFlushing/Disabled-24

• 🟩 avgHeapInUse(Mb) [-7.612MB; -1.402MB] or [-11.127%; -2.049%]

[ManuelPalenzuelaDD]

LGTM, left a minor nit

[eliottness]

Merging on behalf of @tonyredondo