(feat) internal/civisibility: add support for file environmental data

[tonyredondo]

What does this PR do?

V2: (fix) internal/civisibility: add support for file environmental data - v2

This pull request introduces significant changes to handle environmental data more effectively in the CI visibility module. The changes include adding a new environment variable, refactoring the code to improve the handling of CODEOWNERS files, and implementing functions to read, apply, and write environmental data.

Environment Data Handling:

• Added a new environment variable CIVisibilityEnvironmentDataFilePath to store the path to the environmental data file (internal/civisibility/constants/env.go).
• Implemented functions to read and apply environmental data from a file, including getEnvironmentalData, applyEnvironmentalDataIfRequired, and writeEnvironmentalDataToFile (internal/civisibility/utils/file_environmental_data.go).
• Updated the createCITagsMap function to apply environmental data if available (internal/civisibility/utils/environmentTags.go).

Codeowners File Handling:

• Refactored the GetCodeOwners function to use a new helper function parseCodeOwners for better readability and error handling (internal/civisibility/utils/codeowners.go).

These changes enhance the CI visibility module by making it easier to manage and apply environmental data, improving the robustness and maintainability of the code

Motivation

This feature helps on those scenarios where the tests are built in a host machine and then executed in an isolate environment. With this feature we can store the environmental data at build time, and then load it at run time.
In this file we plan to store the data related to the CI provider and Git info required by the test optimization product.

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: tony/add-support-for-file-environmental-data
Commit report: 100cc09
Test service: dd-trace-go

✅ 0 Failed, 5487 Passed, 72 Skipped, 11m 36.42s Total Time

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-03-27 10:23:37

Comparing candidate commit 447536c in PR branch tony/add-support-for-file-environmental-data with baseline commit ba03925 in branch main.

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

scenario:BenchmarkSetTagMetric-24

• 🟥 execution_time [+5.143ns; +8.017ns] or [+4.347%; +6.777%]

scenario:BenchmarkSetTagString-24

• 🟥 execution_time [+6.127ns; +9.153ns] or [+5.362%; +8.010%]

scenario:BenchmarkStartRequestSpan-24

• 🟩 execution_time [-33.974ns; -32.706ns] or [-7.006%; -6.745%]